Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
get help, because the long term implications on maintainability. For example if in 3 years the client wants a new feature and it's not possible because you did't knew what you did when designing the db sheme. Would be pretty shit?
also consider using graphQL for more flexibility and future proofing.
wiwe22106402yHave a look at some best practices regarding databases and make sure to find a good workflow that allows for quick changes in your database structure.
Orm is very nice to use
willol14452yDon't think of databases as having a fixed designed schema, that's waterfall bullshit. Whatever orm you're using probably handles migrations.
Don't build layer per layer, build feature per feature always in the simplest way possible. That's how to "get shit done"
mszaf1952yAlso just search for a sql primer. Then some basic db theory stuff: er relationships, indexing, etc.