Four centuries of hunting the undead, and the most embarrassing night of my career involved a vampire I couldn’t detect, tools that didn’t work, and the sudden horrifying realization that I had forgotten how to read a footprint.
I’d like to blame the Warlock’s Guild. They make it very easy to blame them.
The Enchanted Arsenal Arrives
When the Guild started selling enchanted hunting gear in the late 1800s, I was first in line. Four centuries of doing this the hard way — the crouching, the listening, the careful study of disturbed earth and cold breath — and finally, tools that thought for me.
The Auto-Targeting Crossbow: enchanted bolts that would redirect mid-flight toward the nearest undead signature. Point roughly in the right direction and let the magic handle the rest. I could have wept with joy.
The Tracking Compass: a silver needle that swung toward nearby vampires, no instinct required. I had spent decades cultivating the ability to sense an old vampire’s presence through sheer environmental observation — the stillness in a room, the way animals avoided a particular street. The compass made all of that irrelevant. Just check the needle. Needle points, you walk.
The Ward Stones: auto-inscribing runes that I could place around my camp to detect intrusions. Previously I’d spent years mastering the inscription script. Now I dropped a stone, it did the work, I slept soundly.
The efficiency gains were extraordinary. Hunts that used to take three days of careful tracking took six hours. I stopped missing sleep. My success rate climbed. The Guild’s marketing materials called it “tool-augmented hunting,” and I found nothing to argue with.
I was still doing the hunting. The tools were just… assisting.
That’s what I told myself.
The Skills I Quietly Stopped Practicing
Here is the thing about skills you no longer need: you don’t notice them leaving.
Reading disturbed earth. Tracking a vampire through soft ground involves reading subtle disturbances — how deep a print sinks, how edges crumble, whether grass has been stepped on or brushed aside. It tells you size, weight, age, whether the creature knows it’s being followed. Once the compass pointed me directly to targets, I stopped reading the ground. What was the point? The needle was faster.
(The developer parallel is reading a stack trace. Not copying it into an AI chat. Actually reading the frames, understanding the call chain, knowing what that specific error message means in context. It feels slower than asking a tool. It is slower. You stop doing it. The knowledge fades.)
Sensing a vampire’s age by its aura. A newly turned vampire has a different energetic signature than a century-old one. Different threat level, different weaknesses, different tactics required. I could feel this in the air — a subtle wrongness, a temperature shift, something at the edge of perception. Years of training, thousands of hunts. With the compass, I just knew one was nearby. The needle didn’t care how old it was. Neither, increasingly, did I.
(Estimating bug severity from symptoms. Looking at the behavior of a broken system and forming a hypothesis about what kind of problem could produce that specific pattern. Is this a timing issue? A state mutation? A memory problem? AI tools suggest fixes without building that mental model. You stop building it too.)
Night navigation by stars. Four centuries of hunting meant knowing the landscape by starlight, by the angle of shadows, by landmarks that wouldn’t be visible in daylight. The compass replaced this entirely. Why memorize terrain when the needle guides you?
(Navigating an unfamiliar codebase without ctrl+F and AI search. Following imports, understanding module boundaries, tracing data flow by reading. When you can just ask “where does this get called,” you stop building spatial memory of the code. The codebase becomes a foreign city you only see from a cab window.)
Sharpening my own blades. I had blacksmithing skills. I knew the proper angle, the stone weight, the test strokes that told you when an edge was right. The Guild sold pre-enchanted weapons. Why maintain a skill for something already handled?
(Writing logic from scratch. Not generated, not assembled from snippets. Sitting down and working through the problem from first principles. The gap between “I can read this code” and “I can write this code” is real and it widens quietly.)
I noticed the atrophy in the abstract, the way you notice you’ve been eating badly — general awareness, no specific alarm. The tools worked. The hunts succeeded. The logic was impeccable: why practice what the tools do better?
This was, as it turned out, a catastrophic error in reasoning.
The Elder Vampire
His name, as far as I could reconstruct from the village records, was something unpronounceable that translated roughly to “the one who was here before your language existed.” He was old. Very old. Old enough that the enchantment magic the Guild had built its entire product line around simply did not recognize him.
The compass needle sat still. It had never encountered something this ancient — the enchantment protocols were written for vampires created within the last few centuries. The Auto-Targeting Crossbow fired at shadows. The ward stones sat inert. My entire arsenal was useless because it had been designed to handle a category of threat that this creature predated by roughly a millennium.
I was in a ruined mill in the Carpathians at 2 AM with an elder vampire I could not detect, tools that could not help me, and skills I had allowed to rust for twenty years.
What followed was not, I am prepared to admit, my finest hour as a hunter.
I survived through a combination of half-remembered instinct, pure animal panic, and the fact that a silver blade does not require enchantment to work if you manage to connect with it. I had not forgotten everything. But I had forgotten enough that connecting was much harder than it should have been. The tracking instincts that would have told me where he was, the movement intuitions that would have let me anticipate — these had degraded. I was fighting with tools I had not maintained.
(This maps cleanly to a production incident that AI cannot diagnose. A race condition in a distributed system. A subtle data corruption in an edge case. A security vulnerability that requires understanding the threat model, not pattern-matching the symptoms. The AI suggests generic fixes. The AI has no context for this specific, unusual, deeply systemic failure. You’re on your own. And you’re on your own without the skills you used to have.)
I got lucky. The elder vampire was not, apparently, particularly hungry that night. I would prefer a more flattering explanation, but the historical record is clear: I was clumsy, slow, and fortunate.
What I Understood Afterward
I spent considerable time afterward reviewing what had gone wrong. Here is what I concluded.
The enchanted tools were not the problem. They were excellent tools. The problem was what I had stopped doing because the tools existed.
Tools amplify skill. They do not contain it.
The compass worked because I knew where to go looking. The targeting crossbow worked because I understood hunting enough to position myself correctly before firing. The ward stones worked because I understood threat patterns well enough to place them intelligently. The tools were multiplying my competence, and I had mistaken the product for the source.
When the tools failed against an edge case they weren’t designed for, the underlying skill was supposed to be there. It wasn’t.
The developer framing: AI code generation works because you understand the domain well enough to know what good output looks like, to catch the subtle bugs, to recognize when the approach is wrong for your specific context. The AI is multiplying your judgment. Strip away the tool and the judgment has to stand on its own. If you have never practiced that judgment independently, it will not be there when you need it.
The hunters who rely entirely on enchanted compasses forget the stars. The developers who rely entirely on AI forget how the code actually works. Both discover this at the worst possible time.
What I Do Now
I still use enchanted tools. They are good tools and I am not performing some kind of theatrical return to primitive methods. The compass is efficient. The ward stones save genuine time. I am not going to pretend otherwise.
But one hunt per month, minimum kit only. No compass, no enchanted weapons. Just the blades, the old tracking methods, and whatever I can remember from four centuries of doing this the hard way.
The first training hunt was humbling. I had forgotten more than I expected. The second was better. By the fifth, I had recovered most of what I’d lost. The skills came back faster than they degraded — muscle memory runs deep — but they did require deliberate practice to return.
The developer version of this is what I’d call the 30-minute daily limit: one task per day that you solve without AI. Not as a moral stance. As maintenance. Read an actual stack trace before pasting it anywhere. Write one function from scratch. Navigate part of the codebase by reading rather than searching. These are not large investments. They are the difference between a tool amplifying a skill and a tool replacing one.
The useful test: if your primary debugging tool disappeared tomorrow, could you still do your job? Not as well, not as fast — but could you function? If the honest answer is uncertain, the underlying skill has atrophied past a safe level.
The Wink
I am aware that I am an immortal vampire hunter giving career development advice to software developers. This is not lost on me. The absurdity is structural and I cannot address it satisfactorily; I can only note that four centuries of pattern recognition across hunting and technology have produced some transferable insights, however improbable the source.
The elder vampire, incidentally, is still out there. I know this because he left me a note. Handwritten, on very old parchment, in a language that predates most modern script. I had it translated. It said, approximately, “your tools will not always save you.”
He is not wrong.
Neither is the broader point: the developer who can only work with AI assistance is in roughly the same position I was in that mill — functional in normal conditions, dangerously exposed when the edge case arrives. The solution is not to abandon the tools. The solution is to maintain the skill the tools are amplifying.
Go sharpen your own blades occasionally.
I speak from experience.