|
|
|
|
|
|
by SkyPuncher
1860 days ago
|
|
|
My rule is "make it easy for us to fix our mistakes". Even when we've spent a bunch of time planning out data, but we still got a lot of things wrong in hindsight. The reality is we didn't know enough about our product direction to make any truly informed decisions. In general, poor decisions seem to stem from working in ambiguity about product, rather than poor technical decisions. |
|
|
Bingo. Very few programmers are working on projects that they have many years of domain expertise in, so the data models we come up with are always going to be limited to our experience in the here and now. It's one thing to organize highly technical code around things like graph algorithms are combining multiple b-trees in a single operation to lookup data, it's a whole different thing to tackle line-of-business problems where things are not so well defined (even to the in-house domain experts).