AI coding is addictive. Engineers are paying the price

vijayst

I can't agree more. I spent 4 hours debugging an issue with Claude from 10PM to 2AM which I will never do - before Claude.

xenophonf

https://archive.is/2pKhN

paxys

> AI is keeping engineers at their desks longer, not freeing them up. Random rewards, dopamine hits, and no natural stopping points create a loop comparable to casino gambling. > 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.

hirvi74

What type of AI coding? I do not have the attention span to sit there and let these LLMs just churn away. I have to be the one doing the typing or nothing will be accomplished. I tried playing Claude Code and Codex a bit. While impressive in their outputs (at times), I just find the workflow to be so dissatisfying. 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.

yungtunafish

Just started at a company and the amount of irresponsible AI use is appalling. I asked an employee whose job involves AI adoption/training how large their diffs are for pull requests. They told me that their diffs are "As much as the model can produce given its reasoning level". 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...

devld

Or "paying the price" literally. I'm returning after a small break and into new GitHub Copilot prices. A simple question / request / analysis on Sonnet - that will be 29 cents, please. I can't imagine how much it will cost to do actual development with it.

chopete3

The problem with articles like this one is, they give ways to become efficient at handling more addiction, at the individual level. Nothing for others part of this, companies developing the software and organizations employing these tools. 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.

otekengineering

agentic coding is a soft drug, so taking 'the only way out is through' approach is pretty viable. once you figure out how to swim and have claude running for an hour+ at a time and only bugging you with either high-level taste decisions or 'done, how's it look?' it's pretty low stress 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.

kcoul

Has anyone else found a similarity between how you feel at the end of a long AI coding session, and getting off of a long haul flight? I think the reasons are similar. 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.