A different kind of tired
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
A developer reflects on six months of heavy AI tool usage and how it shifted the nature of their work. The mechanical difficulty of coding — framework fights, debugging, edge cases — largely disappeared, replaced by harder product and UX decisions. The author describes moving from anxious oversight of AI output to trusting it for non-critical code, while still reviewing anything touching security or payments. A side effect: without the natural fatigue barrier of hard coding problems, it's now harder to know when to stop working. The author also notes a shift in how they price freelance work — billing for judgment and expertise rather than hours of typing.
Table of contents
What I used to get tired fromThe feature I wouldn’t have touched last yearWhy I’m mostly settled nowWhat I missWhat it means for the work I sellWhat’s nextSort: