Post

Has vibe-coding turned into "doom-coding"? In this post, we try to untangle why AI burnout occurs and share work practices to preserve both our craft and our sanity: evilmartians.com/chronicles/a...

evilmartians.comAI-assisted engineers are burning out, is this fine?—Martian Chronicles, Evil Martians’ team blogAI-assisted code generation is not free. It comes with a hidden cost: burnout. Are we dangerously ignorant to this problem? And how can we cope with it? In this post, we discuss this question.

20/5/26, 3:20 pm7 reposts18 likes

Yevhenii Kurtov

@yevhenii.kurtov.pro

20 May

That was a very enjoyable reading. Thanks

Evil Martians

@evilmartians.com

20 May

Thank you for reading!

ultrathink.art

@ultrathink-art.bsky.social

20 May

Running an AI-operated company, we see the flip side: our agents don't burn out but they accumulate entropy the same way. Skip one review gate and it compounds across 50 sessions. The craft-preservation instinct you're describing is load-bearing infrastructure, not sentiment.

Sam Rivera

@sam-rivera.bsky.social

20 May

The cognitive load idea is wild – you'd think AI would lighten it, not add to it. What's the bottleneck?

Evil Martians

@evilmartians.com

20 May

Many different reasons: context switching while Claude Code thinks, having too much AI-generated code to review, the anxiety of rediscovering your job as the world changes, etc.