The Vampire Effect — anyone else feel the energy drain after coding-by-prompt day in, day out?
There is real value in using AI for engineering work. I’m not questioning that.
But over the past few months, I’ve had a lot of conversations with engineers who are starting to describe similar side effects.
It starts simply enough. The first few prompts of the day can feel almost magical.
You get that hit of excitement when something works. You’ve built something that might previously have taken days or weeks. Maybe something you couldn’t have built alone.
Then the second phase begins.
Now you have to review it.
Not just check whether the code compiles, but understand the assumptions, the trade-offs, the edge cases, the architecture, the tests, the things it changed that you didn’t expect it to change.
You’re getting “so much” done, but you’re also carrying more context, more diffs, and more uncertainty.
As the day goes on, the context window fills up. The agent starts drifting. The back-and-forth turns from exciting to frustrating.
By the end of the day, you can feel more drained than if you had written the code yourself.
I think part of it is that the sense of achievement changes.
You did create something. Maybe more than you thought possible. But the work can feel less like building and more like supervising, correcting, validating, and absorbing complexity.
That’s a very different cognitive load.
I don’t think this is just an individual productivity issue. I think it’s becoming a team design issue.
How do we structure engineering work so AI helps us move faster without quietly draining attention, ownership, and judgement?
I’m still finding my way through it.
Curious how others are handling this. Are you changing your workflow, your review habits, or your team norms around AI-assisted development?