Code Review Is Not About Catching Bugs (www.davidpoll.com)

submitted 4 days ago by codeinabox@programming.dev to c/programming@programming.dev

5 comments fedilink hide all child comments

Code review answers: “Should this be part of my product?”

That’s a judgement call, and it’s a fundamentally different question than “does it work.” Does this approach fit our architecture? Does it introduce complexity we’ll regret in six months? Are we building toward the product we intend, or accumulating decisions that pull us sideways?

you are viewing a single comment's thread
view the rest of the comments

[-] MagicShel@lemmy.zip 31 points 4 days ago

If something gets to code review before this question is answered, I can't help but feel something has gone dramatically awry.

[-] codeinabox@programming.dev 3 points 4 days ago

I agree but it depends on how teams create and refine their tickets. For example, you could have high level tickets, and someone picks one up and creates an implementation that's not an appropriate fit for your architecture.

[-] org@lemmy.org 5 points 4 days ago

Brass said they want a feature by the end of the week. So, make it happen—regardless of your opinion.

this post was submitted on 23 Mar 2026

16 points (86.4% liked)

Programming

26250 readers

653 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev