25 ms·
For the love of God, critically think about your database schema and object model at a very detailed level, taking into account likely future requirements. I ca
by Aqueous 5y ago
For the love of God, critically think about your database schema and object model at a very detailed level, taking into account likely future requirements. I can’t emphasize enough how important having the correct data shape is from the beginning. This is something you cannot ‘iterate on.’ You have to nail it from the get go, especially the parts central to your application. It’s either right or it isn’t and as soon as it is baked throughout your entire codebase it is too late to change.
I am currently refactoring a giant system that had a badly normalized object model that couldn’t be extended and have been doing so for over a year.
- 331c8c71 5y ago> This is something you cannot ‘iterate on One can use views and modification triggers to split the public interface and a private implementation of a db. Whether it's feasible or worthwhile - it depends of course... It doesn't help with migrating the production dbs though and it's because of this I generally agree with your sentiment.
- iman453 5y agoAny books you would recommend to get better at this?