this post was submitted on 28 Sep 2026
77 points (95.3% liked)
Technology
88342 readers
4339 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 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Agents for generation, humans for review
One, that sounds truly miserable.
Two, there is a decent body of evidence to suggest that this method does not actually speed up development unless you go full lights out software factory which... Why would you want to do that?
https://ide.mit.edu/insights/ai-productivity-and-roi/
EDIT: As an aside this actually reminds me of the Xerox park study into efficiency gains for keyboard heavy workflows vice mouse heavy workflows. Keyboards were perceived as faster by subjects but when actually measured the mouse was faster.
That's just because I need to stop and appreciate my efficiency for 10 seconds every time it saves me 10 seconds :-)
You joke but that's basically the conclusion of both the newer agent studies and the older Xerox park study on peripheral use. Language and logic are stored in an easier to access location in the brain than the kinds of skills used in architecture and planning.
To be clear, I'm no rube. I recognize that these are powerful tools. But I suppose my take here is that if an LLM is necessary to get rid of a lot of the boilerplate and setup for a task that indicates we should explore how we're doing the task.
What I want to see is using these tools not to delegate our problem solving but finding ways to enhance and accelerate it and I don't think writing spec sheets is the answer.
I think you're correct, the amount of rigor in your prompts seems orthogonal from whether you're using them for architecture or implementation.