Artificial Intelligence1 min read

Ask HN: Are you tired too in this AI era?

By · Published by Everything Blog

In short

The burden of constant context switching, continuous guardrailing, and rapid decision-making has offset many of the productivity benefits promised by artificial intelligence. To mitigate this fatigue, some programmers deploy Claude Web for initial planning while assigning Claude Code to run independent reviews and evaluate errors by blast radius. However, human intervention remains mandatory because these models regularly introduce architectural defects, patch over underlying issues, and misdirect focus within repositories. Consequently, software engineering roles are changing from direct technical problem-solving into systems that monitor output velocity against hard-pinned tests.

Key points

  • Professionals are enduring significant cognitive fatigue to meet shifting industry expect…: Professionals are enduring significant cognitive fatigue to meet shifting industry expectations and keep their jobs.
  • Automated code generation frequently introduces structural errors, patches over bugs, and…: Automated code generation frequently introduces structural errors, patches over bugs, and misallocates focus across projects.
  • Developers must rely on immutable, hard-pinned tests to prevent artificial intelligence s…: Developers must rely on immutable, hard-pinned tests to prevent artificial intelligence systems from compromising codebase quality.

Sources checked by our analysis pipeline: 1

Although AI lets us do much more, I feel considerably more tired than before.

We need to keep track of many things happening in parallel and read enormous amounts of generated text. The constant guardrailing, decision making, and context switching overload me.

I am pretty sure most of you are experiencing the same as me, but:

Have you found ways of using AI without increasing mental overload?

I would love to hear your tips, but still be relevant in this AI era, so my boss does not fire me.

Claude Web works differently than Claude Code. I use Claude Web/Chat for briefs, general overview of the project outside of code/app, for planning and handing off the work to Code, that includes prompts. Code is tasked to output a detailed view of what it found, run measurements and tests (designed both by me and Chat) and report findings back. That is fed back to Chat and I get a rough summary. Errors are categorized by their blast-radius and so on.

Eventually I do a deep dive of what changed, how well…

Artificial Intelligence