In San Jose, California, there's a mansion with a staircase that climbs seven flights and ends flat against the ceiling. There's a door on the second floor that opens to a two-story drop into the garden. A cabinet runs through thirty rooms. At one point there were as many as 500 rooms, 2,000 doors, 10,000 windows — and one shower. If you've inherited a vibe-coded codebase, none of this should surprise you.
The Winchester Mystery House was built by Sarah Winchester, widow of the firearms magnate, from 1886 until her death in 1922. She inherited a fortune worth over $500 million today and she used it to hire carpenters to work around the clock for 38 years. She designed the rooms herself, one at a time, with no master plan. Legend says she held nightly séances to receive the next day's building instructions from spirits. The workforce never questioned the specs – they just built whatever was asked.
The result was a structure that grew enormous and became worthless. Sarah spent $5.5 million on the house. After her death, it was appraised at $5,000. In 1975, workers discovered a sealed room nobody knew existed — two chairs and a phonograph behind a locked door, walled off and forgotten as construction continued around it.
The parallels to vibe coding aren't subtle. An LLM generates whatever you ask for without questioning whether it's structurally sound, reasonable, wasteful or wrong-headed. The cost of adding more is nearly zero, so there's no natural friction from resource constraints that forces you to ask whether you should. And because nobody fully understands what was generated three prompts ago and why, everything becomes load-bearing by default. Ignoring technical debt becomes easy because you aren't the one interacting with it directly, and AI isn't incentivized to take these detours on its own. The forgotten room behind the locked door? That's the module nobody remembers writing, walled off by newer code, still sitting in production.
The Winchester House had 47 fireplaces but only 17 chimneys. It was vast, ornate, and structurally incoherent. It demos beautifully — tourists have visited for over a century — but nobody could live in it as a functioning home. Sound familiar?
The lesson isn't "don't use AI to write code." The lesson is that unlimited resources without an accountability system produce the same result every time: something impressive from the outside that's uninhabitable from within. The tool isn't the problem. The absence of someone willing to say "this staircase goes nowhere, tear it out" is the problem.
Sarah Winchester had the resources, the labor, and the inspiration to build forever. What she didn't have was anyone who told her no. If your codebase has the same arrangement, you're not building software. You're building a mystery house that precipitously depreciates. Work with your team or with a properly guided AI agent to pause and consider the long-term cost when the immediate cost is zero.
