53
this post was submitted on 08 Oct 2026
53 points (73.5% liked)
Technology
88677 readers
3726 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
No, it's not really closer to 60/40.
You can deliver the core of the product - the 80% - in the indicated 20% effort zone, aka a few days.
As for not knowing the code... I actually do read what's being output. Just because I'm not familiar enough with the language or framework to write it myself with confidence, it doesn't mean I don't understand it.
Beyond that, the review loop I described above incorporates experts that are language/framework specific to spot issues. Static analysis can easily spot unused code paths - plus that gets covered by tests too, so any leftover is spotted. And even further, after each MVP cycle (which I use in place of sprints as sprints are for human effort cycles which LLMs don't really have, so managing actual target goals instead of physical time periods makes more sense), I have a multi-model (as in, different models from different sources, not just e.g. "all Claude but using Sonnet, Opus and Fable", but more like "Opus 5.5 and GPT 6.1 Sol and [insert currently best model for language]") quorum of experts review the code, test it end to end, find unit/integration/e2e/UI test gaps, write up everything as big/chore tickets, and have another go of the main loop fix those. Same for documentation, it's kept up to date in the same loops.
You get 80% there by being a software engineer to start with, without proper discipline and experience in the field it won't be 80/20.