5 ms·
Yeah, why spend hours on the most important part of the application and likely the most important part of the business when you can gloss over with with an ORM
by mnm1 6y ago
Yeah, why spend hours on the most important part of the application and likely the most important part of the business when you can gloss over with with an ORM and not worry about designing the database until it comes back to bite you in the ass when you can no longer grow your business because of the incredibly stupid thing you did which is not designing your database. Frankly, those businesses deserve to fail if this is the kind of idiocy that drives their decisions. But hey, we got the app going really quickly before going bankrupt.
- zbentley 6y agoI suppose they deserve the same fate if they didn't get security right from day 1? Or accessibility? Or monitoring? Analytics? GDPR compliance? Etc.? Businesses are confronted with different problems at different times. Insisting that everything be solved/designed perfectly up front is silly.
- mnm1 6y agoNone of those things can even remotely compare to the importance of the database design for most software businesses, especially ones just starting out. Most of them can also be addressed later in the company's life unlike a bad database design.
- ulisesrmzroche 6y agoDB design is not the most important part of a business nor the application. This is a very misinformed view point. I've never seen a business go bankrupt because of the DB, but I've seen plenty never make it to market because all their money was burned in development. This is stupid and a great example of how shitty engineering can doom a project. Most important thing is to determine if people are actually gonna buy your app, if you can make a business out of it. Like it or not, marketing is the most important part of the business.