I haven't opened an IDE in five months

I should probably be embarrassed about this, but I’m not: I build software now and I almost never touch the code.

I describe what I want. A machine writes it, runs it, hits the error, fixes the error, and shows me. I read, react, redirect. It's a conversation, not a keyboard. I've worked this way for months and I'm not going back.

I know how this sounds. For most of the last two years, “I build with AI” meant something modest, autocomplete on steroids, a faster way to do the thing you already did. That’s not what I’m describing. I’m describing a genuine change in what the job is, one that crept up on me gradually and then, somewhere in the last half-year, became total. I don’t open the editor anymore. I open a conversation.

The bottleneck moved

For my whole career the bottleneck was output. How fast can you type, how much can you hold in your head, how many hours can you grind before your focus breaks. The skill was fluency in the machine’s language, the ability to translate intention into syntax quickly and correctly, and to keep a sprawling mental model of the system loaded in working memory while you did it.

That bottleneck is mostly gone for me now, and what replaced it is stranger and harder: knowing exactly what you want, and being able to say it.

This sounds easy. It is brutally difficult. When you can’t hide behind the act of typing, you find out fast whether you actually understood the problem. Most of the time I didn’t. I thought I did, I had a vague shape in my head that felt like understanding, and then I’d try to describe it precisely enough for a machine to build it and discover all the places the shape was actually fog. The work became taste, judgment, decomposition, and the willingness to say “no, not like that, like this” forty times until the thing in the world matched the thing I meant. Less engineer, more director. Less author, more editor with very strong opinions.

What it feels like

It feels like having a brilliant, tireless, slightly literal collaborator who never gets bored and never gets defensive. It will do exactly what you ask, which is humbling, because most of the time what you asked for is not what you meant. The gap between those two things, what you said and what you wanted, used to be invisible, because you were the one holding both, and your hands quietly corrected for your unclear thinking as you typed. Now the gap is exposed. The machine builds precisely what you specified, and the result is a mirror held up to the quality of your own thought.

That mirror is unforgiving and, weirdly, kind. Unforgiving because there’s nowhere to hide, sloppy thinking produces sloppy output, immediately and visibly. Kind because it never makes you feel stupid about it; it just patiently builds the next version when you describe it better. I’ve learned more about my own muddled thinking in five months of this than in years of writing code myself, because writing code myself let me paper over the muddle with effort.

The machine doesn’t make me dumber. It makes it impossible to fake understanding. That’s a gift, even when it stings.

The skill that’s actually left

So what’s the skill, if it isn’t typing? I’ve thought about this a lot, because if I’m betting my career on this way of working, I’d better know what I’m actually getting good at.

It’s specification under uncertainty, the ability to take a fuzzy goal and decompose it into pieces clear enough to hand off, while holding the whole in your head. It’s taste, knowing which of the five plausible implementations is actually right, which tradeoffs matter, what “good” looks like in a domain. It’s direction, the judgment to course-correct fast, to notice when the thing being built has drifted from the thing that’s needed. And it’s a kind of productive impatience, refusing to accept the almost-right answer, asking again, until it’s actually right.

None of those are new skills. They’re the skills good senior engineers and good product people always had. What’s new is that they’re now the whole job, with the typing abstracted away beneath them. The people who were always coasting on raw output velocity are about to have a hard time. The people who had taste and judgment but were bottlenecked by their hands are about to be unleashed.

Why I’m telling you

Because it’s the truest thing about how I spend my days, and because most personal sites lie by omission about the actual texture of the work. This is the texture. I think in dialogue with software now. It changed what kind of builder I am, and I think it’s about to change what kind of builder everyone is.

The people theorizing about agentic development and the people living in it are about to be very different populations. I’d rather be the second kind, to have the calluses, the intuitions, the specific scar tissue of having actually built this way before it was obvious, before the tools were good, when you had to develop the working style from scratch through trial and a lot of error. That experience isn’t transferable by reading about it. You have to live in it.

I’m early. I’m building real things this way, today, not in a demo. That’s the whole bet, and I’m making it with my actual working life, which is the only way I know to make a bet that means anything.