Trouble maker and Problem solver ⚙️🔧
Loves simplicity, hates bullshit 💩.
Productivity obsessed, avid learner 🖥🚀
Sport and outdoor freak 🧗⛰
Metalhead 🎸🤘 Father of 2 👨👩👦👦
Opinions are my own
I kinda expected this comment :-)
i don't have a strong opinion about it. we had a similar project 3 years ago where we used plain SQL scripts and it was quite straightforward at the beginning, but as the project grew we ended up with lots of boilerplate, redundant code, very hard to debug parts and writing complex performant queries was also quite difficult, especially for junior/regular fullstack dev ( which normally don't have a deep understanding/knowledge of DBs).
With the latest project we gave ORM a try and I really like how easy it was to set up tables/models. ( and even with migration / changes to the tables) i find it interestingly easy. Furthermore you have a lot of utilities ready and validation and hooks and the "language" is easier to grasp for devs.
Of course this comes to a cost, learning how that specific library does things ( because Sequelize is different from TypeORM for example) and it generally keeps you away from understanding the real thing ( pure SQL) which imho is more important. (that's why i started digging a lot in the debugging part and in the generated queries ) .
In the end as usual, it is a balance between project size, team member skill level and overall speed/deadlines.
I kinda expected this comment :-)
i don't have a strong opinion about it. we had a similar project 3 years ago where we used plain SQL scripts and it was quite straightforward at the beginning, but as the project grew we ended up with lots of boilerplate, redundant code, very hard to debug parts and writing complex performant queries was also quite difficult, especially for junior/regular fullstack dev ( which normally don't have a deep understanding/knowledge of DBs).
With the latest project we gave ORM a try and I really like how easy it was to set up tables/models. ( and even with migration / changes to the tables) i find it interestingly easy. Furthermore you have a lot of utilities ready and validation and hooks and the "language" is easier to grasp for devs.
Of course this comes to a cost, learning how that specific library does things ( because Sequelize is different from TypeORM for example) and it generally keeps you away from understanding the real thing ( pure SQL) which imho is more important. (that's why i started digging a lot in the debugging part and in the generated queries ) .
In the end as usual, it is a balance between project size, team member skill level and overall speed/deadlines.
Excellent reply! :) Agree with it 100%, might give it a try next time or in a side project and see how it goes.
Thanks I did not consider the scenario of a language/framework being easier to learn for Juniors than actually learning SQL.