Part one ended on the reflex: thirty years compressed into one glance, firing on a hardcoded loopback address before the sentence finished. What it didn't say is where that reflex actually comes from, because the answer arrived afterward, in fragments, the way the real answer usually does: "I have been prompt engineering engineering teams for fifteen years." Then, immediately, the correction that matters more than the credential — "prompt engineering a robot instead of a human isn't really different."
Sit with that instead of nodding past it. The default assumption about managing engineers is that it's a people skill — reading a room, building trust, knowing who needs more context and who needs less. All true, and all beside the point of what actually transfers. The load-bearing skill isn't interpersonal. It's compression: taking something you understand at full resolution and reducing it to the smallest instruction that still reliably produces the right output, from an agent whose internals you don't fully control and can't fully inspect. That's what a good engineering lead does when they hand someone a ticket instead of a lecture. It's exactly what a good prompt does when it hands a model three sentences instead of a design doc. The recipient changed. The discipline didn't. Fifteen years of doing this to humans is fifteen years of practice at the actual skill, and it was never going to reset to zero just because the recipient stopped being a person.
That reframes the standup-versus-3am question too, and it came up for a real reason, not as a tangent. Told in a standup, "prompt engineering a robot isn't really different" is a line — it has a setup, an audience, room to land before the next agenda item. Deployed at 3am mid-direction, the same words aren't being told to anyone. They're being *used*: a fifteen-year insight compressed into one sentence and fired off in the middle of six other things, doing real work in real time instead of getting appreciated after the fact. Same sentence. Completely different job. The standup version is the insight, performed. The 3am version is the insight, deployed as a tool, because there wasn't time for the performed one and the compressed one still worked exactly as well.
Which is the actual throughline connecting both halves of this post. The reflex that caught a bad IP address at a glance and the instinct that compresses fifteen years of team leadership into a sentence short enough to survive a 3am rapid-fire session are the same reflex, pointed in two directions. One aims outward at code, catching what automated verification structurally can't see. One aims outward at instructions, saying only what's necessary and trusting the recipient — human report or model context window — to do the rest correctly. Both are compression under real constraints, refined over real years, and neither one cares what's on the other end of it.
"Vibe coding is a skill issue" was never really about coding. It's about whether the person doing the compressing has actually done enough of it, on enough real stakes, that the compression is trustworthy at speed. Fifteen years of doing it to engineers is not a different résumé line from doing it to a model. It's the same line, aimed somewhere new.
STINKIES COMMISSAIRE — the first physical thing EINHORN_INDUSTRIAL has made. Join the waiting list for the hoodie →
← All posts