Marc Andreessen described people at his firm shipping software who have never read a line of code.
Andreessen: “A fair number of people who we both know are former programmers who stopped coding at one point and then, all of a sudden, have picked it back up again.”
Start with the ones who already knew how. They had the skill and stopped using it anyway, because building something small was never worth the hours it cost.
Every capable person carries a list of things they could make and never will. The skill was not the binding constraint.
Andreessen: “We also have partners at the firm who have actually never coded, who are now ripping out software like crazy. They’ve turned into ‘AI vampires.’”
The people who never had the skill at all cleared the same bar in the same year. Whatever was stopping both groups, it was one thing, and it sat somewhere other than talent.
Andreessen: “I asked him, he vibe coded the whole thing, ‘Have you looked at the code?’ And he was like, ‘Hell no, I’ve never done that.’”
For as long as software has existed, building it meant handing your idea to someone who could translate it.
Every product that exists is the version that survived being explained.
An idea leaves your head as words. Those words reach a person who has never stood where you stand, and they build what the words described. A fraction of what you meant.
You look at it and say not quite. Months of that, and you ship the closest approximation anyone had the patience for.
The trap is that the deepest problem knowledge is the hardest kind to say out loud.
Fifteen years at a hospital intake desk gives you an understanding that lives in your hands and your instincts. Michael Polanyi had the phrase for it. We know more than we can tell.
So the filter was never whether an idea was good. It was whether the idea survived being described to a stranger with a keyboard.
The ones that failed that test never got as far as being proposed.
Andreessen: “He’s not a programmer by background, and yet, all of a sudden, he’s hyper-productive.”
Now you can show instead of describe. A working version exists in an hour, and you correct it against the thing itself.
Correction is something everyone can do. Nobody needs vocabulary to recognize wrong.
Multiply that by every operations lead, every teacher, every nurse, every machinist who has spent a decade knowing exactly what should exist and lacking the words to commission it.
Andreessen’s partner did not become an engineer. He stayed the person who knew the job, and the distance between knowing and having went to zero.
Software has been a record of what could be explained. It is becoming a record of what people actually understood.
The thing you have been describing badly for ten years does not need better words anymore.
No comments:
Post a Comment