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 guide on managing difficult pull request discussions, focusing on setting ground rules, assigning roles, and maintaining productive collaboration.
A developer recounts a massive, poorly-scoped code review and the strategies used to salvage it, emphasizing best practices.
Explains why smaller code reviews are more effective and offers practical strategies for splitting large patches into manageable pieces.
Explores six common strategies for using pull requests on GitHub, from quick merges to detailed reviews and collaborative workflows.
Explores how open source software acts like Yelp, shifting power from publishers to consumers by amplifying user feedback and demanding higher standards.
Practical advice for software teams to reduce merge conflicts and improve collaboration using version control best practices.
A guest post contribution on reading other developers' code to learn different problem-solving approaches and evolving best practices.
A developer describes their ideal workflow, emphasizing code review, CI/CD, and team collaboration for efficient software development.
A guide to providing constructive and respectful feedback during code reviews, using examples from Linus Torvalds and a more positive approach.
The author shares the behind-the-scenes process of writing 'The Hacker's Guide to Python', focusing on practical Python development insights from OpenStack experience.
A developer lists the 7 most common code quality issues found during code reviews, focusing on maintainability and best practices.
A guide to implementing effective code reviews in software teams, covering the benefits, principles, and practical steps for a healthy review culture.
Discusses the need for respectful, professional communication in code reviews, using the Linux kernel mailing list debate as a case study.
A collection of humorous programming fails and silly code mistakes, shared for entertainment and a reminder to double-check your work.
A critique of GitHub's pull request workflow, arguing it's less effective than patch-based systems like Gerrit for serious software contributions.
Explains the concept of 'Jürgenization,' a code quality assurance process inspired by Spring framework's Jürgen Höller.
Compares the committer models and development processes of three Python projects: Unladen Swallow, PyPy, and Django.
Highlights two new Team Foundation Server projects on CodePlex: TeamReview for in-IDE code reviews and TFS Sticky Buddy for project status tracking.
