2017年/01月/06日
数据结构和哲学
And nowhere is bad philosophy more on display than in poorly designed data models. Most database ‘antipatterns’ are philosophical in nature.
This is, I think, not well understood by the majority of programmers and project managers. Even most engineers (read: technicians) who do things the right way can’t always explain the philosophical underpinnings of the right way. This situation is analogous to high school students who know how to use the quadratic formula, but have no idea why it’s meaningful. But while most of those bored teenagers move blissfully away from mathematics without doing anyone any serious harm, programmers without a sense of good philosophy (along with plenty of theology and geometry) move from project to project, wreaking havoc on database after database without any understanding of why things keep breaking. This situation is, of course, compounded by project managers, executives, and pointy-haired bosses of all stripes who don’t rise to the level of software technician, and so don’t even know what the right way is, let alone understand why there has to be a right way in the first place.