Tips for creating high-quality pull requests in open source projects, focusing on communication, style guides, and documentation.
A developer argues for the value of inline code comments as a durable form of documentation, contrasting them with ephemeral pull request discussions.
A software engineer shares four techniques to improve skills beyond learning new frameworks, focusing on problem-solving and impact.
A developer shares their positive experiences with open source, from a first small contribution to learning, job opportunities, and community.
A developer's guide to preventing production incidents through team culture, automated testing, and robust deployment processes.
A developer's update on Sourcehut's progress, including web-based patchsets, and Wayland news like sway improvements and a new book.
A guide to refactoring PowerShell switch statements, demonstrating how to replace them with hash tables for cleaner, more maintainable code.
Developer updates on email-based tools for software development, including web patch review for sourcehut and new email composition in aerc2 terminal client.
A developer shares 10 frequently violated clean code principles, covering naming, comments, duplication, and formatting.
A summary of key talks from Day 1 of the Lead Developer Conference, covering containers, tech leadership, and code reviews.
A guide to implementing effective code reviews, covering tone, automation, and best practices for teams.
A summary of a Python Frederick meetup featuring Christine Lee's presentation on data science tools and features available in Python.
A guide on improving code review communication and avoiding conflict, based on a real-world example of a failed review process.
A guide to improving code reviews by focusing on constructive communication and empathy, treating it as a social process rather than just a technical one.
Argues that code reviews should be a team effort, not a single person's responsibility, to improve quality, share knowledge, and build ownership.
A tech lead's role is to guide the team's future direction, not just write code. Focus on strategy, planning, and empowering engineers.
A guide on how to approach and learn valuable lessons from legacy codebases, distinguishing between good and bad examples.
A guide for open source maintainers on how to gracefully close or reject unwanted pull requests and patch submissions.
A developer recounts a massive, poorly-scoped code review and the strategies used to salvage it, emphasizing best practices.
Practical advice for software teams to reduce merge conflicts and improve collaboration using version control best practices.
