Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AI fatigue is real and nobody talks about it

siddhantkhare.com

Post reply on HN
Print view View original

221–230 of 334 posts

Re: AI fatigue is real and nobody talks about it

#221

Post by krupan »

raincole wrote: post #150
barishnamazov wrote: post #29

This write-up has good ideas but gives me the "AI-generated reading fatigue." Things that can cleanly be expressed in 1-2 sentences are whole paragraphs, often with examples that seem unnecessary or unrealistic. There are also some wrong claims like below: > The Hacker News front page alone is enough to give you whiplash. One day it's "Show HN: Autonomous Research Swarm" and the next it's "Ask HN: How will AI swarms…

> HN homepage is still quite sane. Those Show HN posts aren't the insane part. Insane part is like: > Thank you, OpenClaw. Thank you, AGI—for me, it’s already here. > If you haven't spent at least $1,000 on tokens today per human engineer, your software factory has room for improvement > Code must not be reviewed by humans > Following this hypothesis, what C did to assembler, what Java did to C, what Javascript/Pytho…

This is so disheartening. Time to short more tech stocks

Re: AI fatigue is real and nobody talks about it

#223

Post by [deleted] »

orangepanda wrote: post #39

> What should this function be named? I didn't care. Where should this config live? I didn't care. My brain was full. Not from writing code - from judging code. Does it matter anymore? Most good engineering principles are to ensure code is easy to read and maintain by humans. When we no longer are the target audience for that, many such decisions are no longer relevant.

[deleted]

Re: AI fatigue is real and nobody talks about it

#224

Post by 9rx »

parpfish wrote: post #18

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…

Same here. But, then again, I talk about it all the time, so who knows what the article is trying to get at.

Re: AI fatigue is real and nobody talks about it

#225

Post by Xcelerate »

goostavos wrote: post #135
StilesCrisis wrote: post #115

Earlier quoted context omitted.

"You're not imagining it." I hit back immediately.

Sigh.. same. The real AI fatigue is the constant background irritation I have when interacting with LLMs. "You're not imagining it" "You're not crazy" "You're absolutely right!" "Your right to push back on this" "Here's the no fluff, correct, non-reddit answer"

“You’re not [X]—you’re [Y]” is the one that drives me nuts. [X] is typically some negative characterization that, without RLHF, the model would likely just state directly. I get enough politics/subtext from humans. I’d rather the LLM just call it straight.

Re: AI fatigue is real and nobody talks about it

#226

Post by spacecadet »

tartoran wrote: post #167
amelius wrote: post #144

Earlier quoted context omitted.

Except there is a well-known phenomenon among programmers that commencing to work requires more energy than working itself (*). Every time you chill out and come back to work, you will have to invest that extra bit of start-up energy. Which can be draining. (* probably has to do with reloading your working memory)

Context switching tax.

For some. I have never experienced this myself. All my energy goes into keeping unconsciously destructive people from sabotaging the effort.

Re: AI fatigue is real and nobody talks about it

#228

Post by tux1968 »

dripdry45 wrote: post #213
tartoran wrote: post #165

Earlier quoted context omitted.

That’s vibe coding while high. Probably terrible for assesing the results from Claude

Ballmer curve in full effect

For anyone else that didn't recognize this reference, it's also known as the "Ballmer Peak": https://xkcd.com/323/

Re: AI fatigue is real and nobody talks about it

#229

Post by JeremyNT »

parpfish wrote: post #18

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 have this problem too.

I try to fix it by having multiple opencode instances running on multiple issues from different projects at the same time, but it feels like I'm just herding robots.

Maybe I'm ready for gastown..

Re: AI fatigue is real and nobody talks about it

#230

Post by thunfischtoast »

rubslopes wrote: post #176
parpfish wrote: post #18

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 used to lose myself in focused work for hours. That's changed. Now I'm constantly pulled away, and I've noticed the pattern: I send a prompt, wait for the reply, and drift into browsing. Without SelfControl blocking me, I can't seem to resist. I am certainly more productive with LLMs, but I also feel much more tired (and guilty) after a day of work.

This has been a common pattern for me before LLMs, when my work required constantly rebuilding models or doing small deployments where each task/try took more than ~20ish seconds and less than say 3 minutes. It's enough to pull you out of it but not enough to make a proper break or switch tasks.

I suffered from the problems you describe, grabbing a browser window or my phone which would usually take my attention much longer than the task and it left me burned out at the end of the day.

There are some helper tools, like blocking "interesting" pages (like HN, reddit) on the browser, putting the phone in the bag at the end of the room or using a pomodoro timer so sequence proper breaks. But at the end the only thing that really helped is getting into meditation: I try to use these little interruptions of flow as a opportunity to bore myself. Try to reframe boredom from being an annoyance that needs to be fought to a chance to relax your brain for a couple of seconds and refocus.

The want to grab the phone is hard at the start, but it gets better very soon when you manage to push through the discomfort in the first days.

Post reply on HN