Writing

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.

Articles

90K+

Readers on LinkedIn

5 posts tagged “code review”

career growthcode review

The Habits That Make an Engineer Worth Routing Work Through

Every team has one or two engineers other people route work through, and what they have in common is not raw technical strength. It is that when something is given to them it comes back, and when it will not, you hear about it early. Fifteen habits that build that reputation, none of which require a title or permission.

Sep 8, 20260

career growthsystem design

The Defaults I Would Learn First as a Software Engineer

Every roadmap for learning software engineering is the same technology list in a different order, and it tells you nothing about what to do when you are sitting in front of an unclear requirement on a Wednesday afternoon. Fourteen situations you will keep meeting, paired with the move that is usually right, from prototyping a vague requirement to blaming the system rather than the person.

Jul 29, 20260

code reviewtesting

Six Rules That Keep a Codebase Worth Working In

Every one of these gets quoted as an acronym in code review, usually by somebody who read the expansion and not the reasoning, and applied without judgement they produce worse code than if nobody had heard of them. Separation of concerns, DRY, KISS, YAGNI, test driven design and writing for the next reader, each with the thing it protects against and the way it goes wrong.

Jul 2, 20260

devopstesting

What Actually Happens Between Your Pull Request and Production

Most engineers learn CI/CD as a sequence of buttons rather than a system, which works right up until the pipeline goes red and nobody knows which stage failed or why it matters. The five stages walked through one at a time, what each is protecting you from, why builds pin their versions, the difference between rolling, blue green and canary releases, and the ten second skill of reading a failed stage.

Jun 25, 20260

career growthcode review

What Actually Changes in Your First Two Years as an Engineer

Interviews test the small part of the job that is easy to test, and the rest is learned on site. Reading code as the main skill, how to ask a question that costs nothing, why small shipped changes beat large ones in progress, using code review as the fastest teaching you will get, and the four things that actually get people promoted, three of which are not about writing code.

Jun 25, 20268

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. Every session is free; a few slots open each week.