The Passionate Coder·Jun 12, 2025Phase 3: Is the Pull Request Ready for Review?Apply a tailored “ready for review” checklist to ensure the PR is in a state where detailed code review will be productive.
The Passionate Coder·Jun 12, 2025Keep Your Tests Close: Why Tests Belong in the Same Pull RequestTests should be included in the same pull request as the code changes they test.
The Passionate Coder·Apr 7, 2025When PRs Can’t Be Small: Strategies for Making Large Code Changes ReviewableWhen a PR can’t be small, it’s on the author to keep it reviewable — because reviewable PRs lead to better code.
The Passionate Coder·Feb 3, 2025The First Phase of Code Review: ReconnaissanceFor effective and efficient code review, first focus on understanding the problem, gathering context, and ensuring basic functionality.
The Passionate Coder·Dec 6, 2024Why Draft PRs Are a Developer’s Secret WeaponBy sharing in-progress work, you can invite early feedback, integrate with CI tools, and foster trust and transparency within your team.
The Passionate Coder·Nov 4, 2024The Case For Early Code ReviewsEarly code reviews, when used thoughtfully and aided with clear communication, save time and improve team morale.
The Passionate Coder·Oct 7, 2024I’ve Submitted My Code For Review, Now What?After I submit a PR for review, it remains my top priority until it’s fully integrated into the codebase.
InHackerNoon.combySteve Konves·Jul 11, 2017Code Review for Real People“Peer code reviews are the single biggest thing you can do to improve your code” — Jeff Attwood
Oomph, Inc.·Mar 28, 2017Conversational UI: Should a Chatbot be on your Roadmap for 2017?We’ve dreamed about having conversations with our computers for a long time. Stanley Kubrick’s 1968 film 2001: A Space Odyssey imagined a…
