you want spec, I give spec

Someone handed me a customer and a spec request. It’s a small thing, and I think it’s the shape of the next ten years of work.

The handoff was about as casual as they get. A colleague who owns the sale passed a customer to me: here, deal with this, get them a spec. No ceremony. Later he checked whether I was comfortable doing it.

I gotchu.

I’m an infrastructure person. Twenty years of systems, not quotas. Five years ago that handoff would have been strange. The spec would have gone to a solutions engineer, who would have asked me questions in a meeting, who would have turned my answers into a document the account owner could put in front of a buyer. Three people, two handoffs, a week.

Now it’s one person and an afternoon. I know the system. A model drafts the shape of the document, the pricing language, the parts a buyer expects to see. I spend my time on what only I can check, which is whether the thing we’re promising will run. Nobody needed a meeting about the meeting.

The handoff didn’t cross a department line. It crossed a skill line, and the skill line got cheap.

Everyone keeps telling this story backwards. The usual version is that AI replaces the specialist. Cute. What I see is the opposite. AI does the generalist work around a specialist well enough that the specialist can step across into a neighbouring job. The engineer can write the spec. The salesperson can prototype the demo. The writer can ship the script.

Generalize far enough to get across, then go deep where it matters. Both halves get easier at once. The model covers the 70% of a neighbouring discipline that is formatting, convention and boilerplate. You bring the 30% that is judgment, and you bring it from somewhere real.

That combination makes a ridiculous amount of value per person. It also does something less comfortable to say out loud: it filters out low performers, in every discipline at once.

Not the narrow experts. Not the broad dabblers. The people who get handed the customer and say that’s not my job. For thirty years that sentence was a boundary. Now it’s a confession.

The excuse used to be real. Crossing into sales, or design, or finance meant months of learning the vocabulary before you were useful, so staying in your lane was reasonable. That cost is close to zero now. When stepping across is cheap, declining to doesn’t look like focus anymore. It looks like you’d rather not.

Someone I was talking to brought up a line from a philosopher, roughly: get very good at a lot of things, or at a few things that connect. Don’t be the kid who is incredible at the piano and can’t play a sport or use a computer.

I used to read that as advice about being well-rounded. I read it differently now. The piano kid isn’t in trouble because the piano is a bad skill. He’s in trouble because his skill has no edges that touch anything else, so nothing can carry him across. Interconnected is the word doing the work. A few things that connect let you walk from one to the next. With a model handling the parts you don’t know yet, that walk gets shorter every year.

This is new to all of us. It also isn’t, and anyone acting shocked hasn’t been paying attention. Every tool cycle does it. The spreadsheet put finance into every manager’s hands, the cloud put the datacenter on every developer’s credit card, and each time the people who did well were the ones who picked up the thing next to their job. The ones who filed a ticket about it are a footnote.

So when someone hands you a customer and asks for a spec: you want spec, I give spec.