this post was submitted on 10 Mar 2026
50 points (98.1% liked)

Programming

26022 readers
285 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

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
50
The Reviewer Isn't the Bottleneck (rishi.baldawa.com)
submitted 2 days ago by codeinabox@programming.dev to c/programming@programming.dev
13 comments fedilink hide all child comments
 

When you call the humans who keep production safe “the bottleneck” you’re painting a very specific picture. The reviewer as the obstacle. The gate as friction. Something to route around. Cue in the Balrog scene from Lord of the Rings. That picture determines what you build. The tools to remove reviewers look different from tools to support them.

you are viewing a single comment's thread
view the rest of the comments
[–] robojeb@lemmy.world 7 points 2 days ago

Ideally you can do that, but even the most well designed software ends up needing a larger refactor/reorganization that will touch a large portion of the code base.

My boss likes to say "you aren't qualified to design something until you have built it once" which I do feel rings true. This inevitably leads to at least one major redesign for a significant codebase.