this post was submitted on 05 Apr 2026
90 points (96.9% liked)

Programming

26476 readers
270 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
90
If you thought the speed of writing code was your problem - you have bigger problems (debuggingleadership.com)
submitted 6 days ago by codeinabox@programming.dev to c/programming@programming.dev
15 comments fedilink hide all child comments
 

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

Comments

top 15 comments
sorted by: hot top controversial new old
[–] pHr34kY@lemmy.world 35 points 6 days ago (3 children)

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 3 points 6 days ago

Or by word processors.

[–] melfie@lemmy.zip 2 points 6 days ago (1 children)

Quality is speed.

[–] wewbull@feddit.uk 3 points 4 days ago

Slow is smooth. Smooth is fast.

[–] curiousaur@reddthat.com 2 points 6 days ago

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.

[–] vermaterc@lemmy.ml 17 points 6 days ago (2 children)

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.

[–] thedeadwalking4242@lemmy.world 16 points 6 days ago (1 children)

It's all I see slop enthusiasts go off of

[–] squaresinger@lemmy.world 5 points 6 days ago

This. Managers with no coding experience love this.

[–] iekedemos@lemmy.zip 9 points 6 days ago

Prime example: microslop

[–] Hexarei@beehaw.org 6 points 6 days ago

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.

[–] vga@sopuli.xyz 1 points 4 days ago* (last edited 4 days ago)

My problem is that as I grow older and older, I find it harder and harder to be arsed to write any code. LLM fixes that problem beautifully.

[–] m532@lemmygrad.ml 2 points 5 days ago (1 children)

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.

[–] Kissaki@programming.dev 2 points 4 days ago

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?

[–] MousePotatoDoesStuff@lemmy.world 1 points 6 days ago (1 children)

That's part why I don't use VIM for software development, even though I love the motions.

It's a perfect solution... for the wrong problem.

(Other reasons are:

  • I like the features that help me handle the code and catch mistakes before running it

-I paid for the entire RAM and I'm going to use the entire RAM )

[–] FizzyOrange@programming.dev 2 points 4 days ago

Vim's solution to fast editing also isn't very compelling since multiple cursor editing was invented. You can get 90% of the editing speed by learning 1% of the shortcuts. And the UX is slightly nicer since you get immediate feedback.