There's No Limit to How Bad Code Can Get

There is no limit to how poor code can become, according to a former Amazon engineer. The metaphor of a codebase sinking like a ship is misleading because a business can fail long before the code quality reaches a hypothetical end. Technical debt has no reset button, making the situation perpetual. Metaphors implying an end provide a false sense of security.

The code can always become worse, with new layers of indirection or decreased performance emerging over time. The engineer recounts their experience joining Amazon, where a seemingly simple order processing system grew into a massive, unwieldy codebase that became nearly impossible to maintain. Fear suppressed efforts to simplify the system, leading to a tangled web of service dependencies that made tracing behavior difficult.

Despite attempts to fix the architecture, new fixes were always grafted onto the existing system, causing a never-ending cycle. The engineer acknowledges that while a software failure can be catastrophic, the impact depends on factors such as the company's financial health. They emphasize that the sinking ship metaphor is flawed because software exists in an abstract domain, unlike physical structures that can collapse when overbuilt.