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 guide explaining what files to add to your .gitignore file, covering OS files, application files, and credentials to keep Git history clean.
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.
Explores how enterprises can adopt open source development workflows, like public bug trackers and transparent collaboration, to improve software quality and efficiency.
Discusses the benefits and challenges of adding telemetry to open source libraries to improve maintenance decisions.
A practical guide on shipping functional software, covering human-centered design, mastering core languages, avoiding hype, and maintaining consistent coding styles.
A former Presidential Innovation Fellow shares five core principles for successful government IT projects, focusing on culture, user needs, and modern development.
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.
Explores the 'Zen of GitHub,' a set of guiding principles that shape GitHub's engineering culture and decision-making processes.
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'.
Explores how government IT procurement is evolving from waterfall to agile methods and aligning with open source development practices.
Explains why applying closed-source, meeting-heavy workflows to open source projects leads to failure and advocates for asynchronous, transparent collaboration.
Explains best practices for copyright notices in open source projects, covering dates, copyright holders, and legal necessity.
