The Problem with Solid Software
Traditional software is solid — it has a fixed shape defined at development time. Change the requirements and you break the shape. Add a new use case and you either wedge it awkwardly into the existing architecture or rebuild from scratch. The rigidity isn't a bug in the engineering; it's a consequence of the model: humans specify, humans implement, humans maintain.
Solid software has served us well for fifty years. But the emergence of language models capable of reasoning, planning, and writing code has created an opportunity to build systems that behave fundamentally differently — systems that are, in a word, liquid.