this post was submitted on 23 Mar 2026
701 points (99.0% liked)
Technology
83102 readers
4384 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
If you're unable to brute-force verification (research, testing, consulting the ancient texts), there's where you stop what you're doing, and take a breath. Then, consult an expert. Just like the film critic analogy, it's easier to verify than to create, so you're saving the expert time and effort while learning about something that you were obviously already passionate enough about to have started this endeavor.
As someone who codes, it's not always easier to verify than to create.
As someone who codes, I specifically didn't say "always" because of course it's not always true. Especially in the cases of "garbage in, garbage out."
But there's still an argument to be made for mental load and context, for which I'd argue that planning solutions and then writing the code generally is more taxing than someone handing you suggested solutions with semi-complete code or pseudo-code, and then identifying road blocks.
On the other hand, if someone you trust unexpectedly hands you hallucinated garbage, then you're likely to spin your wheels trying to identify what they did.