this post was submitted on 05 Apr 2026
103 points (98.1% liked)

Programming

26402 readers
332 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
top 8 comments
sorted by: hot top controversial new old
[–] vga@sopuli.xyz 1 points 40 minutes ago* (last edited 39 minutes 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. I have 20+ years experience so it kinda works. If you don't have it might not, at the current moment.

[–] pHr34kY@lemmy.world 37 points 1 day 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.

[–] melfie@lemmy.zip 1 points 1 day ago

Quality is speed.

[–] MonkderVierte@lemmy.zip 3 points 1 day ago

Or by word processors.

[–] curiousaur@reddthat.com 2 points 1 day 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.

[–] MousePotatoDoesStuff@lemmy.world 3 points 1 day 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 1 points 49 minutes 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.

[–] Hexarei@beehaw.org 4 points 1 day 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.