I said this a few times here. Tech is never to make the life easier for the worker. It is to make the worker more productive and product more competitive. Moving from horses to cars did not give you more free time. Moving from telephone to smartphone did not give more fishing time. You just became more mobile, more productive and more reachable.
AI fatigue is real and nobody talks about it
151–160 of 334 posts
Re: AI fatigue is real and nobody talks about it
#152Earlier quoted context omitted.
Why do you think author used ChatGPT to write this? It has human imperfections and except this 'The "just one more prompt" trap' I didnt think it was written by a prompt
Author here: Sir, it is almost fully written by human and english/grammar improved by AI
> Distill - deterministic context deduplication for LLMs. No LLM calls, no embeddings, no probabilistic heuristics. Pure algorithms that clean your context in ~12ms.
I simply do not believe that this is human-generated framing. Maybe you think it said something similar before. But I don't believe that is the case. I am left trying to work out what you meant through the words of something that is trying to interpret your meaning for you.
Re: AI fatigue is real and nobody talks about it
#153I keep pushing the ai to do absolutely everything to a fault and instead of spending 10mins to manually correct a mistake the ai made i spend hours adjusting and rerunning the prompt to correct the mistake.
I’m learning how to prompt well at least.
Re: AI fatigue is real and nobody talks about it
#154Re: AI fatigue is real and nobody talks about it
#155> The reason is simple once you see it, but it took me months to figure out. When each task takes less time, you don't do fewer tasks. You do more tasks. > AI reduces the cost of production but increases the cost of coordination, review, and decision-making. And those costs fall entirely on the human. The combination of these two facts is why I'm so glad I quit my job a couple of years ago and started my own business…
Re: AI fatigue is real and nobody talks about it
#156I really feel this. I can make meaningful progress on half a dozen projects in the course of a day now but I end the day exhausted . I've had conversations with people recently who are losing sleep because they're finding building yet another feature with "just one more prompt" irresistible. Decades of intuition about sustainable working practices just got disrupted. It's going to take a while and some discipline to…
Totally my experience too. One last little thing to make it perfect or something that I decide would be "nice to have" ends up taking so much time in total. Luckily now I can access the same agent session on my phone mobile browser too so I can keep an eye on things even in bed. (Joke but not joke :D)
Re: AI fatigue is real and nobody talks about it
#157Instead of managing code , you're now managing AI entities . Managing people has always been emotionally and psychologically exhausting. Managing AI entities can be even more taxing. They're not human beings.
Or we're being managed to refine models
Re: AI fatigue is real and nobody talks about it
#158We’re all still getting the hang of it. I keep pushing the ai to do absolutely everything to a fault and instead of spending 10mins to manually correct a mistake the ai made i spend hours adjusting and rerunning the prompt to correct the mistake. I’m learning how to prompt well at least.
Prompting isn't a real skill and you're not learning anything.
"Claude 4.5 Sonnet operator" is not a job description.
Re: AI fatigue is real and nobody talks about it
#159For me the fatigue is a little different— it’s the constant switching between doing a little bit of work/coding/reviewing and then stopping to wait for the llm to generate something. The waits are unpredictable length, so you never know if you should wait or switch to a new task. So you just do something to kill a little time while the machine thinks. You never get into a flow state and you feel worn down from this c…
Re: AI fatigue is real and nobody talks about it
#160I’ve noticed this strongly on the database side of things. Your average dev’s understanding of SQL is unfortunately shaky at best (which I find baffling; you can learn 95% of what you need in an afternoon, and probably get by from referencing documentation for the rest), and AI usage has made this 10x worse.
It honestly feels unreasonable and unfair to me. By requesting my validation of your planned schema or query that an AI generated, you’re tacitly admitting that a. You know it’s likely that it has problems b. You don’t understand what it’s written, but you’re requesting a review anyway. This is outsourcing the cognitive load that you should be bearing as a normal part of designing software.
What makes it even worse is MySQL, because LLMs seem to consistently think that it can do things that it can’t (or is at least highly unlikely to choose to), like using multiple indices for a single table access. Also, when pushed on issues like this, I’ve seen them make even more serious errors, like suggesting a large composite index which it claimed could be used for both the left-most prefix and right-most prefix. That’s not how a B{-,+}tree works, my dude, and of all things, I would think AI would have rock-solid understanding of DS&A.