*Published July 24, 2026* --- The tools didn't threaten my career. They threatened my identity. After 20+ years building self-worth around writing code, I now mostly direct an AI that writes code. The job listings still say "developer," but the job content has fundamentally changed. I'm an orchestrator now, not an implementor. That's what made the transition uncomfortable. --- For years, my professional identity was built around being the person who knows. Memorized APIs. Internalized patterns. The developer others came to with questions. The moments I knew the answer off the top of my head and a teammate looked impressed. I derived actual self-worth from this. Not just job security. The first time I watched AI write code I would have written, I expected to feel threatened. Instead, I felt nothing. The threat came later, when I understood what the nothing meant: the thing I'd built my identity around wasn't as central as I believed. --- I used to be an implementor. I typed code. My fingers knew the APIs. The rhythm of development was write-test-debug-commit. Now I'm an orchestrator. I steer AI through problems. I verify output. I capture patterns. The rhythm is prompt-review-verify-refine. The strange part: I'm more productive than ever, but I code less than ever. That sentence would have confused me two years ago. What changed is the whole shape of the work: writing code became reviewing code I didn't write, memorizing APIs became verifying the AI's claims about them, the expertise I kept in my head became expertise I keep in skills files, and being the person who knows became being the person who verifies. --- The job listings haven't caught up. They still ask for "React experience" when the real requirement is being able to verify AI-generated React. They ask for "5 years of Python" when what they need is someone who can spot the moment the AI hallucinates a Python API. Orchestrator is the best word I've found for the work, and it appears in exactly zero job descriptions. So I still say "developer" on LinkedIn, and the content behind that word is nothing like what it meant five years ago. --- Here's what I didn't want to admit: some of my resistance wasn't about the tools. AI does make mistakes. Verification is essential. Those are legitimate technical concerns. But sometimes my resistance felt disproportionate to the actual problems. I'd reject output that worked. "I don't trust it" sometimes meant "I don't want this to work." That wasn't skepticism. That was self-protection. My self-concept depended on typing speed, memorized syntax, being the person with answers. So AI wasn't just a tool. It was a threat. Everything I'd built my identity on, it did faster. --- Here's what the hype cycle won't tell you: high automation requires high expertise. AI democratizes access to expert-like output. Anyone can generate plausible code. But you still need expertise to verify it's correct. When AI generates code, I can tell within seconds if it's good: that method signature looks wrong for this framework version, that's not how our state machine works, that test won't catch the edge case we actually hit. I can tell because I already know. Without that knowledge, I'd accept the plausible-looking wrong answer. The identity shift isn't from expert to novice. It's from expert-who-implements to expert-who-verifies. The expertise requirement stays. --- The skills still matter. What I know about system design, architecture, quality. Only how I apply them has changed. Verification is real work. Orchestration is real skill. The cognitive load didn't decrease. The responsibility didn't decrease. Only the visible effort changed. I tell myself these things. Some days I believe them. Other days I watch AI generate in seconds what would have taken me an hour, and I flinch. Not at the quality. The output is correct. At what it implies: that the hour I would have spent wasn't as valuable as I believed. That the identity I built around it was thinner than I knew. I'm not done with this transition. I don't think "done" is the right frame. The old identity doesn't get replaced cleanly. It gets layered over. Some days the orchestrator feels natural. Other days I catch myself writing code by hand just to prove I still can. The hardest part wasn't learning the tools. It was sitting with the question they forced: if the thing I was proud of can be automated, what was I actually proud of? I don't have a clean answer.