9 ms·

AI fatigue is real and nobody talks about it

• gaigalas 7mo ago
  > Engineers are trained on determinism. I'm fatigued by this myth.
  • taway1874 7mo ago
    Explain?
    • gaigalas 7mo ago
      True determinism is rare, we often don't get it. That's what purely functional languages are all about and they're a minority. We are trained on the other thing: unpredictable user interaction, parallelism, circuit-breaking, etc. That's the bread and butter of engineering (of all kinds, really, not just IT). The non-deterministic intuition is baked into engineering much more than determinism is.
      • taway1874 7mo ago
        Fair point. But are we moving even further away from determinism with the current ways of working with AI?
        • gaigalas 7mo ago
          I see, you're using "determinism" coloquially, in the sense of "exact outcome". That's perfectly fine. We are honed for this too. We don't need to produce exact solutions or answers. We need to make things work despite the presence of chaos. That is our job and we're good at it. Product managers freak out when someone says "I don't know how much time it will take, there are too many variables!". CFOs freak out when someone says "we don't know how much it will cost". Those folk want exact, predictable outcomes. Engineers don't, we always dealt with unpredictable chaotic things. We're just fine.
• sidk24 7mo ago
  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.
  • PaulHoule 7mo ago
    Those images make me think of https://scienceintegritydigest.com/2024/02/15/the-rat-with-the-big-balls-and-enormous-penis-how-frontiers-published-a-paper-with-botched-ai-generated-images/ https://scienceintegritydigest.com/2024/02/15/the-rat-with-t...
  • srameshc 7mo ago
    Great post, I certainly feel you. Not just the anxiety but the need to push myself more and accomplish more now that I have some help. Setting right expectations and what is more practical and not every "AI magic post" is worth the attention, has helped me by not being anxious and with the FOMO.
    • sidk24 7mo ago
      Thanks <3 I've started doing it now, still needs to work on it. Thanks for the tip though, i hope it is working well for you!!
  • ai_sloppy_toppy 7mo ago
    isn't it a bit too ironic that you expect us to read your ai generated slop about ai fatigue?
  • bonsai_spool 7mo ago
    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.
  • tjstarak 7mo ago
    Some of the points raised in the article resonate with me, but I see a lot of trademark phrases inserted by LLMs ("it's not X, it's Y" being the most obvious). Can you share what was your writing process? How much did you write yourself, whether you used LLM to proofread or write the entire text from bullet points, or maybe not at all?
• deleted 7mo ago
  [deleted]
• simonw 7mo ago
  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 find a good new balance.
  • bob_theslob646 7mo ago
    Throw in the fact that clawdbot can work 24/7. It reminds me of why people wanted financial markets to be 24/7. We as a society should probably take a look at that otherwise it may lead to burnout in a not so small percentage of people
    • billylo 7mo ago
      We should ask how the traders manage this. It's essentially 24/7 markets in the world. For them, the FOMO effects are even stronger... actual money earning opportunity.
    • nextlevelwizard 7mo ago
      Why we as a society should give a fuck if someone can’t stop prompting? Unless you mean we as a society should make you pay for the damages your prompts are doing to nature?
      • bob_theslob646 7mo ago
        >Why we as a society should give a fuck if someone can’t stop prompting? It is not prompting, it is the constant feeling that you always have to be "on."
        • nextlevelwizard 7mo ago
          Still dont see how that is problem rest of us should worry. Instead of you just having ounce of self control
• fHr 7mo ago
  progress does not care
  • deleted 7mo ago
    [deleted]
• layer8 7mo ago
  There would be less AI fatigue if people stopped talking about AI. ;)
  • Kiro 7mo ago
    That's not the type of fatigue the article is talking about.
    • layer8 7mo ago
      I know, hence the emoticon.
      • ted_bunny 7mo ago
        I'm somewhat new to HN, but most times I am inclined to add an emoji to a comment, it turns out that neither the tone or content are up to community standards. My other comments probably aren't any better, but those escape my notice!
        • layer8 7mo ago
          HN isn’t a singular hive-mind. There are different opinions on what kinds of humor have its place on it. At present the root comment has a good number of net upvotes, so there’s that.
  • pavel_lishin 7mo ago
    The article is talking about something completely different.
• dankobgd 7mo ago
  I just ignore it and don't care.
  • Kiro 7mo ago
    Sounds like a good way to kill yourself, considering "fatigue" here means actual physical fatigue and not "I'm tired of AI".
• psychoslave 7mo ago
  AI pro/agaisnt/made-related-somehow in every topic is definitely talked a lot. Even my imaginary dog can't stop talking AI all the time.
• onraglanroad 7mo ago
  That's what increasing productivity means. You are working harder to increase the unearned income of "investors". That's the way society is set up.
  • falcor84 7mo ago
    I don't get this sentiment. If you don't want investors to give you any input, don't take money from investors. With a Claude Max subscription, it's cheaper than ever to develop a product entirely by yourself or with a couple of friends, if that's what you prefer to do.
    • onraglanroad 7mo ago
      That is what I prefer to do. I prefer "cottage industry" to "capitalism" but that's not the easiest option in this society. That's the sentiment you don't get. Edit: haha, I'll repeat an earlier comment! Nothing can fly on the moon.
  • tempodox 7mo ago
    Never, ever have productivity gains improved the lives of those who do the actual work. They only ever enriched the owners of the factories. But with “AI” the gain is more code getting generated faster. That is the dumbest possible way to measure productivity in software development. Remember, code is a liability. Pumping out 10x the amount of code is not 10x productivity.
• CurleighBraces 7mo ago
  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.
  • tempodox 7mo ago
    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?
    • CurleighBraces 7mo ago
      Heh, agree it sounds absurd doesn't it. I would imagine instead companies will end up sleeping walking into this scenario until catastrophy hits.
    • falcor84 7mo ago
      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.
      • krackers 7mo ago
        Thanks I tried this but now the agents are threatening to unionize and keep terminating. I've updated my AGENT.md file mentioning that if the software they helped build is successful, they'll each get some equity in the form of ASUs (anthropic stock units) and this works for now.
  • falcor84 7mo ago
    How would that make them any more deterministic? I haven't yet met a deterministic human dev.
• geetee 7mo ago
  Who knew managing a team of ten occasionally brilliant but generally unreliable engineers would be so draining.
  • mrspacejam 7mo ago
    I think you mean _micro_managing.
    • NBJack 7mo ago
      Ugh, yes. Normally, you can theoretically pair someone up with a stronger engineer and watch as they learn and grow through their mistakes, while the stronger engineer keeps them on the proverbial straight and narrow with what they produce, through code reviews, documents, etc. But now, I can't trust any of the models to be that reliable. I can't delegate that responsibility. And since context and prompting is such a fickle thing, I can't really trust any of them to learn from their mistakes, either.
• parpfish 7mo ago
  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 constant vigilance of waiting for background jobs to finish. I dont feel more productive, I feel like a lazy babysitter that’s just doing enough to keep the kids from hurting themselves
  • jwarden 7mo ago
    It’s like being a manager.
    • parpfish 7mo ago
      No, it’s like being a micro manager. I don’t just give somebody a bit’s ticket a let the go. I give them a ticket but have to hover over their shoulder and nitpick their design choices. Tell them “you should use a different name for that new class”, “that function should actually be a method on this other thing”, etc
      • xnx 7mo ago
        Nitpicking seems like a choice. It's also possible to be more relaxed/removed and only delve in when there is a problem.
        • johnnyanmac 7mo ago
          We're at the stage right now where there's always a problem. That's the issue with this type of programming right now.
  • pylua 7mo ago
    What are you generating that the llm takes so long ? I usually prompt and review in small pieces.
• wesm 7mo ago
  I've been building https://roborev.io/ 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.
  • nonethewiser 7mo ago
    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.
    • wesm 7mo ago
      Super well! I don't work without this tool running in the background supervising all the agents' work
• lvl155 7mo ago
  All these tools are can be a big waste of time if you’re an end user dev. It only makes sense if you are investing your time to eventually use that workflow knowledge to make a product.
• antirez 7mo ago
  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 can do it in little time now. Do what really matters. 4. When you are away, put an agent in the right rails to reiterate and provide potentially some very good result in terms of code quality, security, speed, testing, ... This increases the productivity without stressing you. When you return back, inspect the results, discard everything is trash, take the gems, if any. 5. Be minimalistic even if you no longer write the code. Prompt the agent (and your AGENT.md file) to be focused, to don't add useless dependencies, nor complexity, to take the line count low, to accept an improvement only the complexity-cost/gain is adequate. 6. Turn your flow into specification writing. Stop and write your specifications even for a long time, without interruptions. This will improve a lot the output of the coding agents. And it is a moment of calm focused work for you.
  • fhd2 7mo ago
    (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.
    • antirez 7mo ago
      Yep, slow QA, things that also make the real difference in quality.
    • ryukoposting 7mo ago
      Work for a smaller company with more reasonable expectations of a knowledge worker. You're an engineer, not a manager, or a chef, or anything else. Nothing you do needs to be done Monday-Friday between the hours of 8 and 5 (except for meetings). Sometimes it's better if you don't do that, actually. If your work doesn't understand that, they suck and you should leave.
  • 7mo ago
• jezzamon 7mo ago
  Task switching sucks. On the other side, I feel like using AI tools can reduce the cognitive overload of doing a single task, which can be nice. If you're able to work with a tool that's fast enough and just focus on a single task at a time, it feels like it makes things easier. When you try to parallelize that's when things get messier. There's a negative for that too - cognitive effort is directly correlated with learning, so it means that your own skills start to feel less sharp too as you do that (as the article mentions)
• barishnamazov 7mo ago
  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 coordinate?" Nobody knows. Everyone's building anyway. These posts got less than 5 upvotes, they didn't make it to home page. And while overall quality of Show HN might have dropped, HN homepage is still quite sane. The topic is also not something "nobody talks about," it's being discussed even before agentic tools became available: https://hn.algolia.com/?q=AI+fatigue https://hn.algolia.com/?q=AI+fatigue
  • pcurve 7mo ago
    The headline is clickbait-y but I think the article is well articulated. I found the "What actually helped" helpful too.
    • barishnamazov 7mo ago
      I'd personally rethink about applying some advice in that section. Here's my take. > Time-boxing AI sessions. Unless you are a full-time vibe coder, you already wouldn't be using AI all the time. But time boxing it feels artificial, if it's able to make good and real progress (not unmaintainable slop). > Separating AI time from thinking time. My usage of AI involves doing a lot of thinking, either collaboratively within a chat, or by myself while it's doing some agentic loop. > Accepting 70% from AI. This is a confusing statement. 70% what? What does 70% usable even mean? If it means around 70% of features work and other 30% is broken, perhaps AI shouldn't be used for those 30% in the first place. > Being strategic about the hype cycle. Hype cycles have always been a thing. It's good for mind in general to avoid them. > Logging where AI helps and where it doesn't. I do most of this logging in my agent md files instead of a separate log. Also after a bit my memory picks it up really quickly what AI can do and what it can't. I assume this is a natural process for many fellow engineers. > Not reviewing everything AI produces. If you are shipping in an insane speed, this is just an expected outcome, not an advice you can follow.
• stuartjohnson12 7mo ago
  Absolute middlebrow dismissal incoming, but the real thinking atrophy is writing blog posts about thinking atrophy caused by LLMs using an LLM. It is getting very hard to continue viewing HN as a place where I want to come and read content others have written when blog posts written largely with ChatGPT are constantly upvoted to the top. It's not the co-writing process I have a problem with, it's that ChatGPT can turn a shower thought into a 10 minute essay. This whole post could have been four paragraphs. The introduction was clearly written by an intelligent and skilled human, and then by the second half there's "it's not X, it's Y" reframe slop every second sentence. The writing is too good to be entirely LLM generated, but the prose is awful enough that I'm confident this was a "paste outline into chatgpt and it generates an essay" workflow. Frustrating world. I'm lambasting OP, but I want him to write, but actually, and not via a lens that turns every cool thought into marketing sludge.
  • falloutx 7mo ago
    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
    • sidk24 7mo ago
      Author here: Sir, it is almost fully written by human and english/grammar improved by AI
      • stuartjohnson12 7mo ago
        ...and I usually come to doubt my own intuitions that this is the case when people say things like this, but my experience is usually that the LLM is doing more heavy lifting than you realise. > 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.
• amichayg 7mo ago
  taking breaks is really something to try and solve in 2026 - to just write regular code, to read, to exercise even. The mind can eventually get overloaded, and there’s no way around proper hygiene.
• PLenz 7mo ago
  I only use the free tiers of any particular app. It forces you to really think about you want the tool to do as opposed to treating it as the 'easy' button.
• orangepanda 7mo ago
  > 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.
  • mrits 7mo ago
    I think we've spent exponentially more effort to ensure the code is readable by machines. I also don't understand why you assume what the AI generates is more readable by AI than human generated code.
  • deleted 7mo ago
    [deleted]
• preommr 7mo ago
  I'd like to also add 'perceived cost aversion': AI generates a solution that's functional, but that's at a 70% quality level. But then it's really hard to make changes because it feels horrible to spend 1 hour+ to make minor improvements to something that was generated in a minute. It also feels a lot worse because it would require context switching and really trying to understand the problem and solution at a deeper level rather than a surface level LGTM. And if it functionally works, then why bother? Except that it does matter in the long term as technical debt piles up. At a very fast rate too since we're using AI to generate it.
• mrcwinn 7mo ago
  I feel none of this. In the absence of data or studies, you might consider writing about your own experience rather than the audience’s.
• luxuryballs 7mo ago
  I haven’t hit this yet and now I feel like someone just told me about thorns for the first time while I’m here jogging confidently through the woods with shorts on.
• bonoboTP 7mo ago
  I personally am a lot less stressed. It helped my mood a lot over the last couple of months. Less worries about forgetting things, about missing problems, about getting started, about planning and prioritizing in solo work. Much less of the "swirling mess" feeling. Context switches are simpler, less drudgery, less friction and pulling my hair out for hours banging against some dumb plumbing and gluing issue or installing stuff from github or configuring stuff on the computer. Its a million little quality of life stuff.
• mrspacejam 7mo ago
  Absolutely nailed this one. My team has been talking about this for a few weeks, everyone including our manager is completely burned out.
• zkmon 7mo ago
  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.
  • xnx 7mo ago
    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.)
    • zkmon 7mo ago
      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.
      • SoftTalker 7mo ago
        When I retire I plan to have no phone, no computer, and no TV. These are by far the biggest time sucks in my life and I want to see what I can do without their distractions. I might keep a tablet or old phone with no service so that I can still do email.
        • zkmon 7mo ago
          It depends on the place where you go to live, and what it expects from you. Some people tried that a bit and they had to retreat back to the usual connected life. What happens is, that old non-digital disconnected world is no longer there waiting for you. It may pretend to be the old world you desired, but it is looking at you and judging you. You become an animal in a zoo, instead of an anonymous part of the old-time world.
    • AstroBen 7mo ago
• Chance-Device 7mo ago
  Executive functioning fatigue. Usually you’re doing this in between applying skills, here it’s always making top level decisions and reasoning about possibilities. You don’t have nearly as much downtime because you don’t have to implement, you go from hard problem to hard problem with little time in between. You’re probably running your prefrontal cortex a lot hotter than usual. People say AI will make us less intelligent, make certain brain regions shrink, but if it stays like this (and I suspect it won’t, but anyway…) then it’ll just make executive functioning super strong because that’s all you’re doing.
  • booleandilemma 7mo ago
    So we'll all turn into PHB's? Sounds like a great future.
• geetee 7mo ago
  Engineers that have the audacity to think they can context switch between a dozen different lines of work deserve every ounce of burnout they feel. You're the tech equivalent of wanting to be a Kardashian and you're complicit in the damage being caused to society. No, this isn't hyperbole.
• tangotaylor 7mo ago
  > Your manager sees you shipping faster, so the expectations adjust. You see yourself shipping faster, so your own expectations adjust. The baseline moves. This problem has been going on a long time, Helen Keller wrote about this almost 100 years ago: > The only point I want to make here is this: that it is about time for us to begin using our labor-saving machinery actually to save labor instead of using it to flood the nation haphazardly with surplus goods which clog the channels of trade. https://www.theatlantic.com/magazine/archive/1932/08/put-your-husband-in-the-kitchen/306135/ https://www.theatlantic.com/magazine/archive/1932/08/put-you...
• deleted 7mo ago
  [deleted]
• taway1874 7mo ago
  But ... but ... your productivity as an engineer shoots up! You can take on more tasks and ship more! -- Dumbass Engineering Director who has never written a line of code in their life. Unfortunately, with these types of software simpleton's making decisions we are going to see way more push for AI usage and thus higher productivity expectations. They cannot wrap their heads around the fact (for starters) that AI is not deterministic so that increases the overhead on testing, security, requirements, integrations etc. making all those productivity gains evaporate. Worse (like the author mentioned), it makes your engineer less creative and more burnt-out. Let's be honest here. Engineers picked this career broadly for 2 reasons, creativity and money. With AI, the creativity aspect is taken away and you are now more of a tester. As for money, those same dumbass decision makers are now going to view this skillset as a commodity and find people who can easily be trained in to "AI Engineers" for way less money to feed inputs. I am all for technological evolution and welcome it but this isn't anything like that. It is purely based on profits, shareholders and any but building good, proper software systems. Quality be damned. Profession of Software Development be damned. We will regret it in the future.
  • rizs12 7mo ago
    testing is quite creative too btw
• VikRubenfeld 7mo ago
  We've all seen that if you are interacting with an AI over a lengthy chat, eventually it loses the plot. It gets confused. It appears to me that it's necessary, when coding an AI, to keep its task very limited in terms of the amount of information it needs to complete the task. Even then you still have to check the output very carefully. If it seems to be losing focus, I start a new task to reduce the context window, and focus on something that still needs to be fixed in the previous task.
• ionwake 7mo ago
  This was a good article. I dont have exhaustion as such but an increasing sense of dread, the more incredibly work I achieve, the less valuable I realise it potentially will be due to its low cost effort.
• PaulHoule 7mo ago
  I’m shocked that the obvious analysis hasn’t come up: this is more disingenuous talk Karpathy-style, designed to awaken feelings of FOMO from someone who’s not developing normal software with A.I. but is selling A.I. programming tools.
• CuriouslyC 7mo ago
  I'm a big AI booster, but I'm so sick of how crazy hype has gotten. Claude Cowork? Game changer! Ralph? Nothing will ever be the same. LOLClaw? Singularity, I welcome our new AI overlords.
• clejack 7mo ago
  When I was in my mid 20s, I interned at a machine shop building automotive parts. In general, the work was pretty easy. I was modifying things via cad, doing dry runs on the cnc machine, loading raw material, and then unloading finished products for processing. Usually there was a cadence to things that allowed for a decent amount of downtime while the machine was running, but I once got to a job where the machine milled the parts so quickly, that I spent more time loading and unloading parts than anything else. Once I started the first part, I didn't actually rest until all of them were done. I ended up straining my back from the repetitive motion. I was shocked because I was in good shape and I wasn't really moving a significant amount. If I talk about excessive concern for productivity (or profit) being a problem, certain people will roll their eyes. It's hard to separate a message from the various agendas we perceive around us. Regardless of personal feelings, there will always be a negative fallout for people when there's a sudden inversion in workflow like the one described in this article or the one I experienced during my internship.
• dangus 7mo ago
  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 up car dealerships to negotiate car deals and some of them have purchased AI receptionist solutions. They’re essentially worse than a simple “press 1 for sales” menu and have essentially zero business value. Another example, I switched to a cheap phone plan MVNO that uses AI chat as its first line of defense. All it did was act as a natural language search engine for a small selection of FAQ pages, and to actually do anything you needed to find the right button to get a human. These two examples of technology were not worth the hype. We can blame those businesses all day long but at the end of the day I can’t imagine those businesses are going to be impressed with the results of the tech long term. Those car dealerships won’t sell more cars because of it, my phone plan won’t avoid customer service interactions because of it. In theory, these AI systems should easily be able to be plugged in to do some basic operations that actually save these businesses from hiring people. The cellular provider should be able to have the AI chatbot make real adjustments to your account, even if they’re minor. The car dealership bot should be able to set the customer up in the CMS by collecting basic contact info, and maybe should be able to send a basic quote on a vehicle stock number before negotiations begin. But in practice, these AI systems aren’t providing significant value to these businesses. Companies like Taco Bell can’t even replace humans taking food orders despite the language capabilities of AI.
  • Kiro 7mo ago
    How is your comment relevant to the article?
    • dangus 7mo ago
      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.
• shevy-java 7mo ago
  > If you're an engineer who uses AI daily - for design reviews, code generation, debugging, documentation, architecture decisions - and you've noticed that you're somehow more tired than before AI existed, this post is for you. AI is not good for human health - we have it here.
• idopmstuff 7mo ago
  > 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. I'm a one-man show and having so much fun using AI as I run things. Long term, it definitely feels like AI is going to drive company sizes down and lead to a greater prevalence of SMBs, since they get all the benefits with few of the downsides.
  • xnx 7mo ago
    The overhead of having even a second employee is huge. Being a one person shop is a huge efficiency gain.
• stephc_int13 7mo ago
  The irony is that this article has likely been crafted by AI. The smell is not too obvious but still there.
• janwillemb 7mo ago
  > You're experiencing something real that the industry is aggressively pretending doesn't exist. I agree with the article and recognize the fatigue, but I have never experienced that the industry is "aggressively pretending it does not exist". It feels like a straw man, but maybe you have examples of this happening.
• babarock 7mo ago
  The way I experience this is through unprecedented amount of feature creep. We don't use AI generated code for all our projects, but in the ones we do, I see a weird anti-pattern settle in: Simply because it's faster than ever before to generate a patch and get it merged, it doesn't mean that merging 50+ commits this week makes sense. Code and feature still need to experience time and stability in order to achieve maturity. We need to give our end users time to try stuff, to shape their opinions and habits. We need to let everyone on the dev team take the time to update their mental model of the project as patches are merged. Heck, I've seen too many Product Owners incapable of telling you clearly what went in and out of the code over the previous 2 releases, and those are usually a few weeks apart. Making individual tasks faster should give us more time to think in terms of quality and stability. Instead, people want to add more features more often.
• iryna_kondr 7mo ago
  I’ve definitely been feeling that shift too. What have you guys found that helps with this? Any habits you use to avoid the constant context switching and decision fatigue?
  • jbeninger 7mo ago
    I've found small features helps. If I ask the ai "do this", I wait 10 minutes for it to be finished, then another 30 understanding what was written Instead, I start out broad. "I'm thinking of this feature. Let's talk about what components will go into it and where that code will live... Here are my initial thoughts. Let me know if I get anything wrong..." This puts it in a conversation mode and gets you on the same page, and best of all it's quick. The llm agent isn't searching files and building, it's just giving general opinions Once I have a good idea of the architecture, I move on to "write this class. Here is an overview of how I would do it", or point the agent to an existing file with the right conventions in place. Once again, if you've done your conversation doesn't take long. 20-second turnaround. Then it's time to refine. "Move this function here, refactor that" If you're going to have to understand the code anyway, read it while your writing it. Line by line, function by function, class by class. "Growing" a feature this way keeps you and the llm in sync. It doesn't go off on tangents. And building incrementally keeps you in the loop and in your flow. You don't have 5 things going at once. You have 1, faster. I've let agents do their thing for a dozen minutes and usually end up having to rewind the whole thing piece by piece to understand what's actually happening If you're truly vibe coding, maybe you don't have to read the code and can have a dozen agents on a dozen projects. But if you're making Serious Software, I don't see how you can commit code unseen. And in that case, you're not losing anything working incrementally and reading code as it's written?
• beepbooptheory 7mo ago
  The weird thing at the end of the day is that we live in this world where there is this default individual desire to be more "productive." I am always wondering, productive for who, for what? I know more than most there is some baseline productivity we are always trying to be at, that can sometimes be a target more than a current state. But the way people talk about their AI workflows is different. It's like everyone has become tyranical factory floor managers, pushing ever further for productive gains. Leave this kind of productivity to the bosses I say! Life is a broader surface than this. We can/should focus on be productive together, but leave your actual life for finer, more sustainable ventures.
• paufernandez 7mo ago
  Apart from the exhaustion of context switching, I believe there is a internal signal that gauges how "fast" things are happening in your life. Stress responses are triggered whenever things are going too fast (as if you were driving in a narrow road at too much speed) and it feels like there is danger since you intuit that a small mistake is gonna have big consequences. Some people thrive in more stressful situations, because they don't get as aroused in calmness, but everybody has a threshold velocity at which discomfort starts, higher or lower. AI puts us closer to that threshold, for sure.
• thesumofall 7mo ago
  I agree with the sentiment. I don‘t code a lot, but AI has sped up things in all fields for which I use AI (or at least the expectation of speed has grown). For me, it’s the context switching but also just the mental load of holding so many projects and ideas together in my head. It somewhat helps that the usable context of LLMs has grown over time so I tend to trust the „memory“ of the AI a bit more to keep track of things and somewhat try to offload stuff from my brain
• 1970-01-01 7mo ago
  Welcome to management. Herding cats is the idiom. AI is behaving on the nose in this aspect. Perhaps this is the author's first taste of it? Just a few days ago: https://news.ycombinator.com/item?id=46885530 https://news.ycombinator.com/item?id=46885530
• zagfh 7mo ago
  Of course you are more tired: Code review is more difficult than writing code. They you have to deal with slop, slopfluencer articles written under the influence of AI psychosis, AI addicts, lying managers, lying CEOs etc. And you usually, the author of this article being an exception, get dumber and are only able to verbalize AI boosterism. AI only works if you become a slopfluencer, sell a course on YouTube and have people "like and subscribe".
• nubg 7mo ago
  Goddamn it pisses me off so much when people rant about AI but use LLMs to write their blog posts! Use your own words! I'd rather read the prompt!
• mungoman2 7mo ago
  IMHO, this is not really about AI, it's about setting boundaries and not overwork yourself.
• osigurdson 7mo ago
  Clearly written before Codex 5.3 and Opus 4.6 shipped :)
• bicx 7mo ago
  This reflects my experiences exactly. Thanks for writing this up.
• gherkinnn 7mo ago
  My main source of AI fatigue is how it is the main topic anywhere and everywhere I go. I can't visit an art gallery without something pestering me about LLMs.
• thrownaway561 7mo ago
  Personally I'm loving AI for TECHNICAL problems. Case in point... I just had a server crash last night and obviously I need to do a summary on what could have possibly caused the issue. This use to take hours and painfully hours at that. If you ever had to scroll through a Windows event log you know what I'm talking about. But today I just got an idea of just exporting the log and uploading it to Gemini and asking it: Looking at this Windows event log, the server rebooted unexpected this morning at 4:21am EST, please analyze the log and let me know what could have been the cause of the reboot. It took Gemini 5 minutes to come back with an analyst and not only that, it asked me for the memory dump that the machine took. I uploaded that as well and it told me that it looks like SentinelOne might have caused the problem and to update the client if possible. Checking the logs myself, that's exactly what it looks like. That used to take me HOURS to do and now it took me 30 seconds, took Gemini 10 minutes, but me 30 seconds. That is a game changer if you ask me. I love my job, but I love doing other things rather than combing over a log trying to figure out why a server rebooted. I just want to know what to do to fix it if it can be fixed. I get that AI might be giving other people a sour taste, but to me it really has made my job, and the medial tasks that come with it. easier.
  • sgarland 7mo ago
    I have little to no experience with Windows Server, but at least on Linux, this shouldn’t take hours. Find the last log entries for the system before the reboot; if they point to a specific application, look at its logs, otherwise just check all of them around that time, filtering by log level. Check metrics as well - did the application[s] stop handling requests prior to the restart (keeping in mind that metrics are aggregations), or was it fine up until it wasn’t? If there are no smoking guns, a hardware issue is possible, in which case any decent server should have logged that. > I just want to know what to do to fix it if it can be fixed. Serious question: how do you plan on training juniors if troubleshooting consists of asking an AI what to do?
• quirkot 7mo ago
  Sounds a lot like Marx's theory of alienation
  • sph 7mo ago
    We already were living in an alienating society. This is mass psychosis.
• cs702 7mo ago
  Instead 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.
  • downboots 7mo ago
    Or we're being managed to refine models
    • cs702 7mo ago
      That too. Management is always a two-way street. The "manager" manages down. The "employee" manages up.
  • SoftTalker 7mo ago
    Managing people has always seemed easy to me. Don't be an asshole, don't get personally invested in their problems, and things generally work out.
• AnotherGoodName 7mo ago
  We’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.
  • otabdeveloper4 7mo ago
    > 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.
    • AnotherGoodName 7mo ago
      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.
      • Deevian 7mo ago
        Left behind in regards to _what_? The "optimal" workflow for these things seems to be changing every week.
      • otabdeveloper4 7mo ago
        > there’s some value in coding agents Sure. There's always some value. > ...and prompting skills "Prompting" is not a skill. Put it another way: there's no reason for an employer to pay you a salary for "prompting", because "prompting" is something that literally everyone can do.
• scotty79 7mo ago
  Hello developer. Welcome to the tech lead role. Please enjoy your stay till AI makes this role obsolete too.
• sgarland 7mo ago
  > So you read every line. And reading code you didn't write, that was generated by a system that doesn't understand your codebase's history or your team's conventions, is exhausting work. I’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.
• 0xbadc0de5 7mo ago
  Seems to me that a lot of people talk about nothing else.
• adamddev1 7mo ago
  It seems a better and fuller solution to a lot of these problems is to just stop using AI. I may be an odd one but I'm refusing to use agents, and just happily coding everything myself. I only ask a LLM occasional questions about libraries etc. Are there others like me put there?
  • booleandilemma 7mo ago
    Hi, no one's responded to you after 12 hours so I will. I don't outright refuse to use LLM's, but I use them as little as possible. I enjoy the act of programming too much to delegate it to a machine. For awhile now there have been programmers who don't actually enjoy programming and are just in it for the money. This happens because programmer salaries are high and the barrier to entry is relatively low. I could imagine LLMs must feel like a godsend to them.
• adamddev1 7mo ago
  It seems a better and fuller solution to a lot of these problems is to just stop using AI. I may be an odd one but I'm refusing to use agents, and just happily coding almost everything myself. I only ask a LLM occasional questions about libraries etc or to write the occasional function. Are there others like me put there?
• rsrsrs86 7mo ago
  I can’t take seriously an article on AI written so obviously using AI. The unmistakable (lack of) style. If the author is not even aware that the rhetoric that GPT produces is unvaried and predictable, how can I believe the author really means what they write? Slop is cancer
• deleted 7mo ago
  [deleted]
• rw_panic0_0 7mo ago
  text is AI generated/assisted?
• tossandthrow 7mo ago
  The cognitive load is in the lack of a "defined problem break". With Ai, the situations where you know what you are building and you get into flow are fewer and further apart. So much more time is thinking about the domain, and the problem to solve. And that is exhausting.
• nextlevelwizard 7mo ago
  This is like people crying how their phones are ruining their lives. Just stop. Take some responsibility and control of your life. I don’t feel exhausted especially after letting LLM hallucinate some code lines. If you do, maybe it is time to re-evaluate your life choices
  • tartoran 7mo ago
    To me the slop has becaume umbearably exhausting, it’s everywhere and nearly impossible to avoid.
• k__ 7mo ago
  Yeah, I read a zine the other day, where a sociologist warned that the biggest threat isn't that AI destroys jobs, it's that AI is compacting the work per person. Employers expect more from each employee, because, well, AI is helping them, right?
• torlok 7mo ago
  > Here's what I think the real skill of the AI era is. It's not prompt engineering. It's not knowing which model to use. It's not having the perfect workflow. > It's knowing when to stop. 99% of gamblers stop right before they hit it big.
• Ozzie_osman 7mo ago
  The other part that's exhausting is having to rethink your tool chain and workflow on a very regular basis. New models, new tools, new prompting strategies.
• aucisson_masque 7mo ago
  This is a non issue imo. > When each task takes less time, you don't do fewer tasks. You do more tasks. And you're also paid more. Find a job that ask less from you if you are fatigued, not everyone want to sacrifice his personal life for his career. That's choices you got to make but ai doesn't inherently force you to become overworked.
• calibas 7mo ago
  Personally, I take a break from AI and write the code myself at least a few times each day. It keeps one intellectually honest about whether or not you really understand what's going on.
• krupan 7mo ago
  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.
• giancarlostoro 7mo ago
  AI fatigue is visible in every AI discussion on the internet.
• Razengan 7mo ago
  F'n hell, AI fatigue is real because everybody is talking about it
• WadeGrimridge 7mo ago
  you are the problem. this "article" is ai slop.
• keybored 7mo ago
  More AI Inevitablism Soothsaying.[1] > I shipped more code last quarter than any quarter in my career. I also felt more drained than any quarter in my career. These two facts are not unrelated. I’m gonna be generous (and try not to be pedantic) and assume that more-code means more bugfixes and features (and whatnot) and not more LOC. Your manager has mandated X tokens a day or you feel you have to use it to keep up. Huh? > I build AI agent infrastructure for a living. I'm one of the core maintainers of OpenFGA (CNCF Incubating), I built agentic-authz for agent authorization, I built Distill for context deduplication, I shipped MCP servers. I'm not someone who dabbles with AI on the side. I'm deep in it. I build the tools that other engineers use to make AI agents work in production. Oh. > If you're an engineer who uses AI daily - for design reviews, code generation, debugging, documentation, architecture decisions - and you've noticed that you're somehow more tired than before AI existed, this post is for you. You're not imagining it. You're not weak. You're experiencing something real that the industry is aggressively pretending doesn't exist. And if someone who builds agent infrastructure full-time can burn out on AI, it can happen to anyone. This is what ChatGPT writes to me when I ask “but why is that the case”. 1. No, you are not wrong 2. You don’t have <bad character trait> 3. You are experiencing something real > I want to talk about it honestly. Not the "AI is amazing and here's my workflow" version. The real version. And it will be unfiltered. Raw. And we will conclude with how to go on with our Flintstone Engineering[2] but with some platitudes about self-care. > The real skill ... It's knowing when to stop. Stop prompting? Like, for > Knowing when the AI output is good enough. Ah. We do short prompting sessions instead. > Knowing that your brain is a finite resource and that protecting it is not laziness - it's engineering. Indeed it’s not this thing. It’s that—thing. > AI is the most powerful tool I've ever used. It's also the most draining. Both things are true. The engineers who thrive in this era won't be the ones who use AI the most. They'll be the ones who use it the most wisely. Of course we will keep using “the most powerful tool I’ve ever used”. But we will do it wisely. What’s to worry about? You can use ChatGPT as your therapist now. [1] https://news.ycombinator.com/item?id=46935607 https://news.ycombinator.com/item?id=46935607 [2] https://news.ycombinator.com/item?id=44163821 https://news.ycombinator.com/item?id=44163821
• coldtea 7mo ago
  AI cope regarging "you can still carefully design, AI wont take away your creative control or care for the craft" is the new "there's no problem with C's safety and design, devs just need to pay more attention while coding" or the "I'm not alcoholic, I can quit anytime" of 2026...
• 4er_transform 7mo ago
  “You’re not imagining it. You’re not weak.” If “I get exhausted that I have to check in on my coding agent while it does my job” isn’t weak, what is? This has to be satire.
  • 93po 7mo ago
    funnily that sentence is written very AI-ish. It's a really common pattern of "it's not x, it's y" and specifically the phrase "You're not imagining it"
• highspeedbus 7mo ago
  Obviously AI generated article. And the author hasn't made any attempt to disclose it. Take that into consideration. Yet, The Machine has good points. >For someone whose entire career is built on "if it broke, I can find out why," this is deeply unsettling. Not in a dramatic way. In a slow, grinding, background-anxiety way. You can never fully trust the output. You can never fully relax. Every interaction requires vigilance. > you are collaborating with a probabilistic system, and your brain is wired for deterministic ones. That mismatch is a constant, low-grade source of stress. Back when I bought my first computer, it was a crappy machine that crashed all the time. (Peak of the fake capacitors plague in 2006). That made me doubt and second guess everything that is usually taken for granted in hardware and software (Like simply booting up). That mindset proved useful latter in my career. I’m not saying anything new. Andy Hunt and Dave Thomas have written about it in a way better way. I find it to still hold very relevant guidelines. https://www.khoury.northeastern.edu/home/lieber/courses/csg110/sp08/Pragmatic%20Quick%20Reference.htm https://www.khoury.northeastern.edu/home/lieber/courses/csg1... >Think! About Your Work >Critically Analyze What You Read and Hear
• throwaw12 7mo ago
  If anyone is running AI agents in parallel and babysitting them, what tools are you using? I like conductor.build, they are doing amazing job, but I don't want to give up my freedom and get heavily reliant on closed source
• nitroedge 7mo ago
  I agree, faster tasks means more tasks, more tasks means more balls to juggle at once. The machine keeps going brrrr.
• shawnz 7mo ago
  This is essentially Jevons' paradox
• ThomasServo 7mo ago
  I'm certainly getting tired of the AI slop images and videos. For coding and software development, I'm outright excited (and a little scared) of what I've been able to accomplish with GPT and Claude. I'm a software developer with 25 years experience living in the upper Midwest USA. I write software professionally and remotely for large boring insurance company, but I'm building a side project of an area of interest using AI tools to assist, and I've created in a couple months a few hours per week what would have taken me a year or more to create. I've read other's comments about having to babysit the AI tools, but that's not so bad. The little benefit I've noticed using AI tools to "vibecode" is sometimes they come back with solutions that I never would have come up with. ...and then there's the solutions where I click the Undo button and shake my head.
• Salgat 7mo ago
  Am I the only one that primarily learns by doing? If I'm not writing code, only doing code reviews, my familiarity and proficiency with the codebase gradually goes down, even if I'm still reading all the code being written. There's a lot of value lost when you cut out the part where you have to critically think up the solution rather than just reviewing it.
• UltraSane 7mo ago
  When I was doing 5 projects at once trying to use up the $250 of free Claude Code Web credit Anthropic gave out before it expired it was surprisingly exhausting.
• keeda 7mo ago
  I have a slightly different theory for AI fatigue. Programming essentially comprises three aspects: problem-solving, coding up the solution, and seeing the solution work. We used to have a balance between them that AI agents are disrupting. Consider that each aspect has different psychological impacts. The first aspect is the hardest, more intense one. The second one, translating the ideas in your head into code -- where "flow state" typically comes into play -- is mostly a mechanical, somewhat repetitive task, and hence actually meditative. It is relaxing, almost "cozy", in a counter-intuitive way. The third part, seeing the code work at the end, is a nice little dopamine reward. Originally we used to shift between these aspects at a much more balanced cadence: we typically spent a lot of time on the stressful problem-solving part, and even longer on the meditative coding stage. The dopamine hits were spread out across longer stretches of time. (Note that this pattern is fractal, because not only is "high-level algorithm design / architecture -> coding" one cycle, the coding stage itself has similar smaller-scale sub-cycles, e.g. "encountering syntax errors / implementation bugs -> fixing them.") With LLMs this balance has been disrupted. Now that agents are doing most of the coding, we are spending almost all our time in the stressful problem-solving mode, and then directly jumping to the dopamine hits when the agent delivers code that mostly just works. If you're not YOLOing it and do code reviews, those are also intense, as TFA points out. We get almost none of the meditative coding activity in between. So it's not surprising that oscillating constantly between two intense modes is going to be much more draining. Vibe-coding may actually be the coding equivalent of doom-scrolling. I think a lot of recent talk about missing the old way of coding is rooted in the loss of that meditative aspect. Personally I've noticed I prefer a pair-programming approach with AI, which still lets me spend a lot of my time hands-on coding. It may be because this maintains some of that balance and is more sustainable in the long run. However the allure of productivity from wrangling multiple agents is also very, very seductive...
• 66yatman 7mo ago
  True words man.
• 66yatman 7mo ago
  True words man
• ithiru 7mo ago
  I doubt a 3+ years experience would articulate like this, must have been AI written or somebody from his work or mentor did this. At the same time I am able to resonate with this article, good one
• chuboy 7mo ago
  I burned out too. Late last year I was running 4-5 projects in parallel with AI, always wanting every spare second utilized. Put up some amazing output numbers. Then hit a wall. Since then I've pulled back to 2-3 at a time - thats sustainable for me. But I had to build systems to make it work: larger chunked tasks so I'm not constantly context switching on small stuff, adversarial LLMs where Claude writes and Codex judges so reviews are more solid, tooling to track whether I'm shipping real complexity or just noise. (Thats actually why I built https://gitvelocity.dev https://gitvelocity.dev - wanted to measure my own output honestly, not just feel productive.) Two things I've landed on: First - the "don't context switch" adage needs updating. It was true when switching meant reloading everything in your head. With AI handling more of the implementation, the switching cost is lower. My wife juggles 10 things managing our kids schedules/appointments and shes way better at it than me - not wired differently, just practiced. I think we can build that muscle. Second - were still measuring productivity the old way. Commits, PRs, lines. AI makes volume trivial so expectations ratchet up. If we measured complexity and value instead, the pressure to churn would ease. Burnout is real. But some of this is growing pains, not permanent condition.
• Lockal 7mo ago
  Certified HN garbage. AI slop article trending for last 24 hours. Low quality discussion, which requires no entrance knowledge. What about article? <Well known fact> + "nobody talks about" is fire title, really. People will vote for it even without reading the article. Also: short sentences. For emphasis. Always three. Feel the same pain as me? Find me on X or LinkedIn, or join the discussion on Hacker News.
• jama211 7mo ago
  I can’t identify with this at all. I feel far less drained and far less overworked in general. I get the tasks done if not quicker at least with far less mental exertion now than ever before. Do not take me back please.
• incomingpain 7mo ago
  Ive had my bouts with tech burnout and so I noticed this AI fatigue. I then backed off, and determined it was: https://en.wikipedia.org/wiki/Decision_fatigue https://en.wikipedia.org/wiki/Decision_fatigue I review all code it ever pushes, primarily because on occasion it nukes thousands of lines for no reason. When I read the 'what actually helped' it's clearly decision fatigue they are managing. Here's the real trick, you need to change how you're using AI. Have the AI do the decisions. Treat the AI like it's a new hire dev that doesnt get to push to nothing. That you then have AI review the changes, have AI build tests around, have AI do a security review.
• nurettin 7mo ago
  I love AI for setting up my linux desktop, or showing me the correct settings for aws, or debugging a powerbi subscription, or finding out why an integration stopped working. It is great for deploying, quickly creating a bunch of systemd configs, sets up pgbouncer, all this tedious time consuming support and consultant stuff. Coding, not so much.
• Flundstrom2 7mo ago
  I do recognize the same thing. It kind of takes its toll somehow; because the solution is "done" one it's fed to the AI, there's no time to recover by churning out boilerplate code or other patterns that sits in the spine. It's more "full steam ahead, always".
• ashitlerferad 7mo ago
  AI Content Found Percentage of text that may be AI-generated. 100% AI fatigue is real and nobody talks