For years I worked one week on rotation doing database support for "developers" while I worked in the database engineering department. For every one legitimate

For years I worked one week on rotation doing database support for "developers" while I worked in the database engineering department. For every one legitimate bug, there were 99 cases where a familiar pattern consistently emerged: - a "developer" did not have sufficient knowledge of a relational database management system: "what is an index and where and how do I create one?" - the "developer" was using object-oriented programming, and writes to stable storage would end up being deserialization of objects; - the "developer" always used an ORM because he either did not know SQL, or his SQL programming skills were poor; - code generated by an ORM was huge: 32 KB of SQL querying every literal value, which of course would cause a huge, completely unnecessary slowdown.