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

31–40 of 334 posts

Re: AI fatigue is real and nobody talks about it

#31

Post by antirez »

fhd2 wrote: post #28
antirez wrote: post #23

1. Make long pauses: 1h of work, stop for 30 minutes or more. The productivity gain should leave you more time to rest. Alternatively work just 50% of time, 2h the morning, 2h the evening, instead of 8 hours. Yet trying to deliver more than before. 2. Don't mix N activities. Work in a very focused way in a single project, doing meaningful progresses. 3. Don't be too open-ended in the changes you do just because you c…

(1) is not something the typical employee can do, in my experience. They're expected to work eight hours a day. Though I suppose the breaks could be replaced with low effort / brain power work to implement a version of that.

Yep, slow QA, things that also make the real difference in quality.

Re: AI fatigue is real and nobody talks about it

#33

Post by wesm »

nonethewiser wrote: post #25
wesm wrote: post #20

I've been building https://roborev.io/ (continuous background code review for agents) essentially as a cope to supervise the poor quality of the agents' work, since my agents write much more code than I can possible review directly or QA thoroughly. I think we'll see a bunch of interesting new tools to help alleviate the cognitive burden of supervising their work output.

You can see the exponential growth of tokens in real time! lol Do you find it works well? With these agents I've found that making the workflows more complicated has severe diminishing returns. And is outright worse in a lot of cases. The real productivity boost I've found is giving it useful tools.

Super well! I don't work without this tool running in the background supervising all the agents' work

Re: AI fatigue is real and nobody talks about it

#34

Post by falloutx »

simonw wrote: post #24
onlyrealcuzzo wrote: post #19

Earlier quoted context omitted.

> 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. My problem is - before, I'd get ideas, start something, and it would either become immediately obvious it wouldn't be worth the time, or immediately obvious that it wouldn't turn out well / how I thought. Now, the problem is, everything starts off so incredi…

I used to have ideas and jot them down in Apple Notes and then usually forget about them entirely. Now I have an idea and jot it down in the Claude Code tab on my iPhone... and a couple of minutes later the idea is software, and now I have another half-baked project to feel guilty about for the rest of time.

In couple of minutes? My claude code takes like 5 mins just to wake up and write a simple plan.

Re: AI fatigue is real and nobody talks about it

#38

Post by pylua »

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…

What are you generating that the llm takes so long ? I usually prompt and review in small pieces.

Re: AI fatigue is real and nobody talks about it

#39

Post by orangepanda »

> 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.

Re: AI fatigue is real and nobody talks about it

#40

Post by falloutx »

antirez wrote: post #23

1. Make long pauses: 1h of work, stop for 30 minutes or more. The productivity gain should leave you more time to rest. Alternatively work just 50% of time, 2h the morning, 2h the evening, instead of 8 hours. Yet trying to deliver more than before. 2. Don't mix N activities. Work in a very focused way in a single project, doing meaningful progresses. 3. Don't be too open-ended in the changes you do just because you c…

1) Is this for founders, because employees surely cant do this. With new AI surveillance tech, companies are looking over our shoulders even more than before.
Post reply on HN