361
AI coders think they’re 20% faster — but they’re actually 19% slower
(pivot-to-ai.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 12 Jul 2025
361 points (95.5% liked)
Programming
21605 readers
211 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
"AI is good for Hello World projects written in javascript."
Managers will still fire real engineers though.
I find it more useful doing large language transformations and delving into unknown patterns, languages or environments.
If I know a source head to toe, and I'm proficient with that environment, it's going to offer little help. Specially if it's a highly specialized problem.
Since SVB crash there have been firings left and right. I suspect AI is only an excuse for them.
Same experience here, performance is mediocre at best on an established code base. Recall tends to drop sharply as the context expands leading to a lot of errors.
I've found coding agents to be great at bootstrapping projects on popular stacks, but once you reach a certain size it's better to either make it work on isolated files, or code manually and rely on the auto complete.
So far I've only found it useful when describing bite-sized tasks in order to get suggestions on which functions are useful from the library/API I'm using. And only when those functions have documentation available on the Internet.