Live data from Hacker News

AI fatigue is real and nobody talks about it

siddhantkhare.com

211–220 of 334 posts

Re: AI fatigue is real and nobody talks about it

#211
post #82

For 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…

I joke that I'm on the "Claude Code workout plan" now. Standing desk, while it's working I do a couple squats or pushups or just wander around the house to stretch my legs. Much more enjoyable than sitting at my desk, hands on keyboard, all day long. And taking my eyes off the screen also makes it easier to think about the next thing. Moving around does help, but even so, the mental fatigue is real!

I've seriously wondered about merging a home office and home gym into one, and doing sets in between claude working. My usual workout has about 22-30 sets of exercises total and I probably wait on Claude that often in a day. It would be wonderful to be able to spread my exercise throughout the entire day. I'd also include an adjustable height desk so that I could be standing up for much of the workout/workday. I could even have a whiteboard in there.

Re: AI fatigue is real and nobody talks about it

#214

For 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…

That’s why now it’s legitimate to work on multiple features or projects at the same time

I tried this but didn't realize how exhausting it is to think about even 2 smaller items at once.

Re: AI fatigue is real and nobody talks about it

#215

Earlier quoted context omitted.

> as i’m learning how to prompt well Prompting isn't a real skill and you're not learning anything. "Claude 4.5 Sonnet operator" is not a job description.

I’m finding fewer and fewer people that need convincing that there’s some value in coding agents and prompting skills at this point. To the point where my reply to this is quite simple; You’ve been left behind and at this very late point in the game i feel no obligation to even try to convince you.

Left behind in regards to _what_? The "optimal" workflow for these things seems to be changing every week.

Re: AI fatigue is real and nobody talks about it

#216
post #2

Author here. Not an anti-AI post. It's about the cognitive cost - faster tasks lead to more tasks, reviewing AI output all day causes decision fatigue, and the tool landscape churns weekly. Wrote about what actually helped. Curious if others are hitting similar walls.

Why did you use an LLM to write/change the words in your blog and your post? It really accentuates the sense of fatigue when I can tell I'm not interacting with a human on the other side of a message.

Re: AI fatigue is real and nobody talks about it

#218
This author puts to words several thoughts of mine that have been jelling recently. In the end I still seems to miss that AI is totally optional. It's a depressing read because the basic gist is, this AI stuff is weird and depressing and addicting to the point of losing productivity, but I have to use it so here are some ways to try and counter those negatives.

Dude! You don't have to use it!! Just write code yourself. Do a web search if you are stuck, the information is still out there on stack overflow and reddit. Maybe us kagi instead of Google, but the old ways still work really well.

Re: AI fatigue is real and nobody talks about it

#219

Earlier quoted context omitted.

That’s why now it’s legitimate to work on multiple features or projects at the same time

This way you can do twice the terrible job twice as fast! (Also, this only applies if what you're working on happens to be easily parallelizable _and_ you're part of the extremely privileged subset of SV software engineers. Try getting two Android Studios/XCodes/Clang builds in parallel without 128GB of RAM, see what happens).

I appreciate sarcasm, but this is just snarky.

But yeah improving build speed & parallel running I think are one of the biggest advances devs can do to speed up development time in the AI age. With native apps that can be a challenge. I restructured a react native project to make it faster to iterate, but I have a feeling you might not be fond of rn.

Re: AI fatigue is real and nobody talks about it

#220
post #117
post #85

I think the fatigue is that the technology has been hyped since long before today when it’s actually started to become somewhat useful. And even today when it’s useful, it’s really most useful for very specific domains like coding. It’s not been impressive at all with other applications. Just chat with your local AI chat bot when you call customer service. For example, I watch a YouTube channel where this guy calls u…

How is your comment relevant to the article?

How is your comment relevant to the article?

My comment is relevant because I’m pointing out, like the article does, that AI isn’t turning out to be anywhere near as useful and low-friction as it has been promised. Hence, the fatigue.

Your comment is the one that contributes nothing.

Post reply on HN