In the end, this is going to create unmaintainable code that no one understands. It also discourages reviewing the code because no dev can meaningfully review 1000s of lines of code in a day while also accomplishing their tasks.

NOTE: I am still pro AI, just like I am pro heavy machinery. I just don't want people to cut off their legs...

On the flight, it's not exactly like you directly feel the wind going through your hair as you travel 1000km/hr, but your body still knows that you did. You feel the lag immediately, not really due to a time zone difference but due to how unnatural it is to move so far in so short a time.

I feel the same way after a highly productive AI coding session. I used to anecdotally mention to others that I liked to maintain and use older machines because it felt nice to get little breaks here and there while the machine took longer to open a browser/app, return search results, render a file, etc. This is the opposite of that. Everything is happening so fast, your mind is taxed differently than if you are responsible for typing everything yourself... no matter how fast you could type code.

That said, I don't think it's entirely my increased cognitive load that makes me feel drained after a session, it's as though you can somehow feel the token burn, the water/electricity use, just as you somehow felt the wind shear on the airplane you were just in for many hours.

Summary of the addiction management tips from the article.

1. Time-box your AI coding sessions with a clear goal and a hard end time.

2. Separate exploration (testing ideas) from execution (shipping code) to avoid losing focus.

3. Prioritize sleep, hard stops, and actual recovery as essential maintenance, not just wellness.

4. Invest in structured training to move from basic usage to advanced multi-agent workflows.

5. Personalize your AI workflow to fit your needs while actively avoiding common anti-patterns.

-

When a developer stops writing code and starts using Claude to handle multiple projects at once, they are essentially managing the outcomes.

They have become 10x engineering managers. The context strain and emotional strain is overwhelming.

if you're overloaded with PRs, build LLM-based systems to take the load off. don't be a senior engineer, be an engineering manager.

> The fix is deliberate habits, not restricted tools. Time-box sessions, separate exploration from execution, and treat recovery as maintenance.

Getting tired of AI slop telling me about AI.

One other aspect of LLMs that I do not enjoy when it comes to development is the fact that LLMs minimize my contributions. I do not feel like I can take credit for anything I create if I technically did not create it.

However, I absolutely adore LLMs for learning new concepts and for troubleshooting. To me, that is where they shine the brightest.