Design philosophy and paradigm discussions
View All Tags
There is a street in my neighborhood where three different utility companies dug up the same stretch of pavement in the same month. First the water company. Then the gas company. Then the internet provider. Each one cut into the ground, laid their pipes, filled it back in. None of them talked to each other. None of them shared a trench.
This is how we build software.
I have built the same application at least a dozen times. Different companies, different industries, different logos on the login screen, but underneath, the same patterns over and over again. User management. CRUD forms. Data tables. Dashboards. State handling. The same architecture decisions, the same boilerplate, the same bugs in the same places.
At some point, I stopped and asked myself: why are we still doing this?
Imagine you could sit down, describe exactly what you want an application to do — in plain language — and it just... builds itself. Not a rough prototype. Not a demo that falls apart when you poke it. A real, production-ready application that works on day one.
That sounds like science fiction. But it is not.
IKEA revolutionized furniture by making it composable, flat-packed, and assembly-friendly. What if software worked the same way?