120
If you thought the speed of writing code was your problem - you have bigger problems
(debuggingleadership.com)
this post was submitted on 05 Apr 2026
120 points (97.6% liked)
Programming
26798 readers
257 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've found the biggest bottleneck is bugs. If you catch a bug during development, it takes the least time to fix.
Catch a bug during PR, you need to fix the code, and the PR needs to happen again.
Catch a bug in QA, and you need to fix the code, do another PR, and get it tested again.
This pattern goes right through UAT, and god help you when a bug makes it to Prod.
There is nothing more time consuming than code that was written quickly.
All code is written quickly these days, and not by humans. The patterns to guard against bugs also help speed development, and are the same we already learned.
Strong typing and test driven development.
Or by word processors.
Quality is speed.
Slow is smooth. Smooth is fast.