Writing on Code review

Articles on Code review from Tauseef Fayyaz: practical writing on engineering, AI and tech careers, drawn from leading a team and mentoring engineers.

By Tauseef Fayyaz60 posts90K+ readers

Follow for new posts

4 posts tagged “code review”

career growth
The Habits That Make an Engineer Worth Routing Work Through
The habits of great software engineers are mostly about reliability, not brilliance. Fifteen learnable habits, from estimating in ranges to labelled review comments and weekly notes, that make you the person work gets routed through.Sep 8, 202641
career growth
The Defaults I Would Learn First as a Software Engineer
Fourteen software engineering best practices written as defaults: prototype vague requirements, choose boring tools, wait for the third duplicate, write the failing test first, measure before optimising, ask after an hour.Jul 29, 202622
code review
Six Rules That Keep a Codebase Worth Working In
Six clean code principles, separation of concerns, DRY, KISS, YAGNI, test-driven design and writing for the next reader, each with what it protects against, where it came from and how it goes wrong.Jul 2, 202656
devops
What Actually Happens Between Your Pull Request and Production
A CI/CD pipeline explained as a system, not a set of buttons: the five stages from pull request to production, what each protects you from, rolling vs blue-green vs canary, and how to read a failed stage in ten seconds.Jun 25, 202657

Browse writing by topic

Every tag has its own page.

Work with me

Stuck on something specific?

Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.