> In the end it means you give the data an elevated role in the system, and you write the code around the data. That's how things are meant to be. The structur

> In the end it means you give the data an elevated role in the system, and you write the code around the data. That's how things are meant to be. The structure of a program naturally follows that of the data it manipulates. > When the code would be cheaper to write or maintain with a different data representation - you can't. Who says that? The real problem is that most programming languages aren't capable of integrating database schemas into the type-checking process, so when you change a schema, it's difficult to make sure applications follow through in a consistent manner. That's what makes change unnecessarily risky and painful. But it's possible to do better than that: http://impredicative.com/ur/ http://impredicative.com/ur/