Explores why developers find Git difficult, contrasting individual vs. team workflows and the mindset shift needed to appreciate it.
A guide for software developers on how to optimize and improve their daily tools like IDEs and command-line utilities through configuration and learning.
A reflection on programmer stereotypes from the essay 'The Little Printf', discussing common traits like chasing new tech and collecting unread books.
Encourages open source contributions by emphasizing that even small fixes like typos are valuable and appreciated by project maintainers.
The article discusses the AMP Project, an open-source framework for building fast mobile web pages, using a story about misaligned incentives as an analogy.
A developer argues against committing commented-out code, explaining why it harms code readability and maintainability.
Author shares the journey and process of writing a book on Python Machine Learning, including productivity tips and the book's focus.
A practical guide on shipping functional software, covering human-centered design, mastering core languages, avoiding hype, and maintaining consistent coding styles.
An interview discussing the importance and ongoing debate around commenting code, challenging the 'comments are a failure' clean code perspective.
Critique of blind review processes for tech conference talks, arguing they lead to conservative selections and overlook speaker skill.
Applies the 'keep your bench clean' principle from cooking to software development, emphasizing clean code, atomic commits, and removing unused code.
A passionate rant arguing for the importance of writing clear comments in code, even when the code itself is well-structured and 'self-documenting'.
Announcement of LibFX 0.3.0 release, a JavaFX utility library with features like transforming collections and tree node streaming.
An essay arguing that 'boring' programming languages are superior for complex, interesting work, contrary to popular tech industry advice.
SUSE's Hack Week allows engineers to work on self-chosen projects, fostering innovation, learning, and collaboration.
A developer shares how starting with a minimal, functional version of a side-project (a Python TODO manager) leads to completion and avoids abandonment.
A blueprint for product management focusing on building trust, establishing velocity, and strategically killing scope to align product and engineering teams.
A developer reflects on the value of functional, working code over perfect architecture, using a collaborative iOS project as an example.
Advocates for establishing a 'Git-iquette'—a set of etiquette rules for using Git in team projects to improve code history clarity and collaboration.
Explains the concept of Ubiquitous Language in software design using a personal medical story to highlight the importance of clear terminology.
