The Palace Problem and AI-Assisted Software Building

We just went from horse-and-carriage to car. The old manuals still have truth in them, but the whole map of effort, speed, and leverage changed overnight. Building used to mean holding an entire system in your head. A fragile memory palace. A house of cards in biological primate RAM. If you stop, the palace collapses. Dinner, a meeting, a context switch. You come back and it’s glass dust on the floor. That’s why builders can look “antisocial.” It’s not vibes. It’s survival. You’re trying to get the palace out of your head and into code before it evaporates. Then the weird miracle: I type a few paragraphs that barely make sense on reread, and the machine builds the palace anyway. It mirrors the structure. It fills the gaps. It hands it back. The feeling is not “wow productivity.” The feeling is: I am seen. Like the part of you that has been translating yourself for 20 years finally gets understood on first contact. This is why the new skill is not “code faster.” It’s taste, direction, and leadership. Managing a swarm of agents. Running tight loops. Knowing what to ask for. And it brings back something old-school: apprenticeship. We forgot how to teach. Now teaching matters again, because the tools are insane but the mind behind them still has to be trained.