Live data from Hacker News

AI fatigue is real and nobody talks about it

siddhantkhare.com

161–170 of 334 posts

Re: AI fatigue is real and nobody talks about it

#161
post #151
post #58

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.

How we use efficiency is a choice. It's possible to work a lot less if you accept quality of life from an older era (no phone, Netflix, etc.)

It's not a choice. For example, Windows XP is no longer a choice, because the context around it made it unsafe now, though it didn't change. Life style from an older era is no longer the norm, which means your relative life quality degrades automatically and it actually becomes unsafe.

Re: AI fatigue is real and nobody talks about it

#162

I loved the section about trying to fight against a system that isn't deterministic. LLMs because of their nature require constant hand-holding by humans, unless business are willing to make them entirely accountable for the systems/products they produce.

How could you hold a dumb machine “accountable”? Attempting that would be insane. How would you discipline it? Reduce the voltage in its power supply? Do you hold the dice accountable when you lose at the craps table?

I'm not saying that it's a good idea, but the obvious way would be with evolution: Give each agent its own wallet, rewarding it for a job well done and penalizing it for a poor job. Then if it runs out of money, it's "out of the game", but if it earns enough to it can spawn off another agent with similar characteristics, and give it some of its money.

Re: AI fatigue is real and nobody talks about it

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

isn't it a bit too ironic that you expect us to read your ai generated slop about ai fatigue?

Re: AI fatigue is real and nobody talks about it

#165

Earlier quoted context omitted.

I know this is a terribly irresponsible and immature suggestion, but what I've been doing is every time I give claude code a request of indeterminate length, I just hit a blunt and chill out. That and sometimes I'll tab into the kind of game that can be picked up and put down on very short notice, here's where I shameless plug for the free and open source game Endless Sky. For me personally, programming lost most of…

Now that’s vibe coding.

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

Re: AI fatigue is real and nobody talks about it

#166
post #5

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

This is real, so im a freelancer, i used this small invoicing platfrom to create invoices for my customers. At "work" im working on accounting systems, and erp-s. So with AI, why would i pay monthly for invoicing when i can build it myself. After i day i had invoicing working. Like the simple thing where you get PDF out. Then i started implementing doube-entry booking. And support different tax systems. And then, but…

"Invoicing for freelancers" has just about as many solutions as "to do" lists or ticket systems. Just use what you built if it works, open sourcing it is likely to get zero interest among the thousands of other options.

Re: AI fatigue is real and nobody talks about it

#167

Earlier quoted context omitted.

I know this is a terribly irresponsible and immature suggestion, but what I've been doing is every time I give claude code a request of indeterminate length, I just hit a blunt and chill out. That and sometimes I'll tab into the kind of game that can be picked up and put down on very short notice, here's where I shameless plug for the free and open source game Endless Sky. For me personally, programming lost most of…

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.

Re: AI fatigue is real and nobody talks about it

#168

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…

> Things that can cleanly be expressed in 1-2 sentences are whole paragraphs

Perhaps the author just likes to write? I've only just recently started blogging more, but I unexpectedly started to really enjoy writing and am hoping to have my posts be more of a "story". Different people have different writing styles. It's not a problem, it's just that you prefer reading posts that are straight to the point.

Re: AI fatigue is real and nobody talks about it

#169

Earlier quoted context omitted.

It reduces the friction of coding tremendously. Coding was usually not the bottleneck but it still took a significant amount of time. Now we get to spend more time on the real bottlenecks. Gathering requirements from end users, deciding what should be built, etc.

> It reduces the friction of coding tremendously. Coding was usually not the bottleneck but it still took a significant amount of time. I don’t think I agree. How can something be both “usually not a bottleneck” that usually “takes a significant amount of time” ? > Now we get to spend more time on the real bottlenecks. Gathering requirements from end users, deciding what should be built, etc. Sounds like you might re…

Just because the magical fairy helps you write things, you still need to ensure it's engineered properly. Especially at the macro level.

Some day it'll handle that, but for now it's very bound to make silly decisions that you need to be on top of, especially as those compound in a large scale system.

Re: AI fatigue is real and nobody talks about it

#170

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…

This. It’s the context switching and synchronicity, just like when you are managing a project and go round the table - every touch point risks having to go back and remember a bazillion things, plus in the meantime you lose the flow state.
Post reply on HN