3 ms·
It depends on the domain. CRUD should be by the numbers, unless you're working at planetary scale. But some domains are very poorly understood. You won't get f
by TheOtherHobbes 7y ago
It depends on the domain. CRUD should be by the numbers, unless you're working at planetary scale.
But some domains are very poorly understood. You won't get far by trying to iterate - because you don't even know what the problem is, never mind how to solve it, and your dirty hack is going to introduce naive assumptions that turn out to be spectacularly wrong.
- smcameron 7y agoThough as John Gall famously said, "A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works and cannot be patched up to make it work. You have to start over, beginning with a working simple system."
- greggyb 7y agoComing from a perspective of the IT consulting world, CRUD apps are rarely that simple. The core is always the same, sure - you're basically wrapping read and write transactions to a storage subsystem in a pretty veneer. The complexity is never in the CRUD actions themselves. But transforming the things that have been R-ed so we can U them or identifying the full population of things to be D-ed is often non-trivial and deeply tied into understanding of the business domain and process at hand. Often (analytics and reporting lenses on here), the complexity is in modeling the data appropriately and the logic of transformation. The work of presenting this stuff to a user is basically trivial arithmetic.