this post was submitted on 14 May 2026
241 points (95.5% liked)
Technology
84816 readers
5921 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Well there's the problem.
I'm a software developer and I say that AI is the greatest force-multiplier that's been introduced into the field since the compiler. I love using it, it handles the most tedious and annoying parts of the process. But there are situations I don't want to use it in, and of course being forced to use would give me a more negative opinion of it. Obviously.
There isn’t any credible evidence out there that actually shows LLMs are a “force multiplier.” That is almost certainly just a made up marketing term for unprofitable chatbot companies.
In this case the evidence is literally first-hand experience. There is nothing that will change my mind on this because it's my direct personal experience from actual use.
I honestly don't care what marketing says, and if other people have different experiences then that's just them. In my personal actual real-world experience I found that they let me get tons more done and their quality of work is perfectly fine as long as you're using the right tools and giving them the right instructions.
The article says that developers are disagreeing with that in situations where they are "forced" to use AI, and that's fair, it doesn't make sense to force a tool to be used for something it's not good at. They might be using it wrong. I use it whenever it's better than not using it, and that ends up being quite often in my workflow.
The right tools is definitely key. Back an eternity ago, like October 2025, there was only Claude IMO if you wanted anything bigger than about a page of code. The others have come a long way - better than Claude was then, and I still feel like Claude is out in front, though by a less dramatic margin now.
As for "the right instructions" - I'd say it's more of "use the right process" which basically involves applying all those best practices that have developed over the past decades for human development, but we old farts from back before their time "don't need all that, it's a waste of time" because, basically, we internally practice most of the discipline without doing the documentation. With the AI tools: document your requirements, your architecture, tool choice selection process, designs, development plan, comment the code with traceability to why the code is being written, unit and integration tests, reviews, lessons learned, etc. etc. Having all that documentation kept with the project, well organized, is key to "bringing the AI agent up to speed" which you may be doing often. They really do demonstrate the eternal sunshine of the spotless mind, so if you have them take the time to write everything relevant down as they go (not just the code), then when a new one comes online it can jump into the middle of a development plan without repeating (as many) mistakes / making (as many) bad assumptions.
To be brutally honest, working with AI coding agents reminds me a LOT of working with overseas programmer consultants - if you don't get everything in writing you're gonna have a bad time.