this post was submitted on 14 May 2026
413 points (97.0% liked)
Technology
84796 readers
3607 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
As a person who works with coworkers who fully embraced it, it doesn't look like they are any faster. There is one group that is faster, but they don't verify their code and provide burden of it on another person who reviews PR to go through their shit code (sorry, but it is unnecessarily complex, does things in weird ways, I've seen it had bugs that even canceled each other (I guess this is probably due to re-running until things work))
I've seen human coders do this quite a bit, even myself - always unintentional, usually brain-bending when you find the first inversion.
I think it is domain of young developers who just want choice to do what they do, but don't care how.
Even you use LLM you often have similar mindset.
I belong to group of people with a weakness that I want to understand every step of the code that I produce. When LLM produces something I need to understand what it does (which takes time) then I realize I could do it better way, so I rewrite it. So LLM just slows me down.
I understand many things clearly, but when it comes to binary yes/no true/false 1/0 type results my brain tends to answer: Yes, it's one of those. I don't think I've made a double inversion "working" error since the 1990s, but I know I've seen others do it - even in Rust.