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.
Quality is speed.
Slow is smooth. Smooth is fast.
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.
This is why my personal use of AI has been focused pretty cleanly on “doing what I already do, more thoroughly” - By not turning it into a “ship more code more faster” machine, it’s a “can explore my code and answer questions and help design things more thoroughly” machine.
I tend to go with “AI-augmented” development because I’m shipping the same things I’ve been shipping - Just with a way to quickly brainstorm and compare ideas on something my team members may not have time for. I can propose my ideas and have some LLM tell me what the downsides of my approach would be - or what I should guard against.
It’s crazy to me that folks are treating them like sources of truth when they should just be an untrustworthy second opinion that is faster than you. I think of it as an intern with speed but questionable taste lol.
What’s in this article is true, but to be honest I’ve never seen anyone using lines of code as an optimization metric. Even among the most AI enthusiastic people. I mean: the author of the article seem to be fighting non-existing problem.
It’s all I see slop enthusiasts go off of
This. Managers with no coding experience love this.
The bigger problem I have is ADHD. I can only keep the focus for a few days, then it’s over. So there’s only two possibilities for me. A: Never get anything done. B: Lower the scope and write code as fast as possible.
I don’t see how you get from “for a few days” to “never get anything done”. What happened to the few days?
Does your typical work need more than a few days of investment to understand what you can reasonably write?
