Small notes from developers who review code. Add yours.
This is a growing collection of real lessons from developers who review pull requests every day. It started as a single article — What Code Reviews Taught Me Over Time — and now it's open for everyone to add their own notes.
The idea is simple: if you've reviewed code and learned something — a habit, a bug you keep finding, a comment you keep leaving — write it down here. The notes can be short. They don't need to be perfect. Real lessons from real reviews.
- Read the article on Medium: What Code Reviews Taught Me Over Time
- Or read it here: ARTICLE.md
- Read contributor notes:
/notes - Add your own notes: How to contribute
You don't need to write a full article. Even one short note is welcome.
- Fork this repository.
- Create a new file in the
/notesfolder. Name ityour-github-username.md. - Write your notes in any structure you like. A few examples below.
- Open a pull request.
That's it. No perfect English required. No long writing required. Real notes from real reviews are the whole point.
See CONTRIBUTING.md for more details and examples.
Anything you've learned from reviewing or being reviewed. For example:
- A bug pattern you keep finding (AI-generated or human)
- A small habit that made your reviews faster
- A comment you keep leaving and wish you didn't have to
- A lesson from a production bug that started in a PR
- A code review story — what went wrong, what you learned
- A tool, linter rule, or workflow that helped your team
Big or small. One line or one page. All welcome.
If these notes helped you, please star the repo so more developers find it. The more people who contribute, the more useful it becomes for everyone.
All content is shared under Creative Commons Attribution 4.0 (CC BY 4.0). You can share, adapt, and use these notes for any purpose, including commercial — just give credit to the contributors.