If you thought the speed of writing code was your problem - you have bigger problems (debuggingleadership.com)
from codeinabox@programming.dev to programming@programming.dev on 05 Apr 09:13
https://programming.dev/post/48319444

cross-posted from: lemmy.bestiver.se/post/1030154

Comments

#programming

threaded - newest

vermaterc@lemmy.ml on 05 Apr 09:48 next collapse

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.

iekedemos@lemmy.zip on 05 Apr 10:58 next collapse

Prime example: microslop

thedeadwalking4242@lemmy.world on 05 Apr 13:24 collapse

It’s all I see slop enthusiasts go off of

pHr34kY@lemmy.world on 05 Apr 12:25 collapse

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.

MonkderVierte@lemmy.zip on 05 Apr 14:25 next collapse

Or by word processors.

curiousaur@reddthat.com on 05 Apr 14:39 collapse

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.