✳flâneur — a map of the web's best reading

How to Do Code Reviews Like a Human (Part One) · mtlynch.io

mtlynch.io · 3,946 words · saved by 1 readers

Lately, I’ve been reading articles about best practices for code reviews. I notice that these articles focus on finding bugs to the exclusion of almost every other component of a review. Communicating issues you discover in a constructive and professional way? Irrelevant! Just identify all the bugs, and the rest will take care of itself. So I had a revelation: if this works for code, why not romance? With that, I’m announcing my new ebook to help developers with their love lives: My revolutionary ebook teaches you proven techniques for maximizing the number of deficiencies you find in your partner. The ebook does not cover: Based on my reading of code review literature, those parts of a relationship are obvious and not worth discussing. Does this sound like a good ebook to you? I’m assuming you just yipped “Nonononono!” So, why is that the way we talk about code reviews? I can only assume the articles I’ve read are from the future, where all developers are robots. In that world, your t

Lately, I've been reading articles about best practices for code reviews. I notice that these articles focus on finding bugs to the exclusion of almost every other component of a review. Communicating issues you discover in a constructive and professional way? Irrelevant! Just identify all the bugs, and the rest will take care of itself. So I had a revelation: if this works for code, why not romance? With that, I'm announcing my new ebook to help developers with their love lives: My revolutionary ebook teaches you proven techniques for maximizing the number of deficiencies you find in your par

Explore this link on the map →

related reading