2 ms·
People can be wary of these bolts-included/on-rails solutions because there is typically hell to be paid as soon as you venture slightly off of the rails. If no
by zamalek 4y ago
People can be wary of these bolts-included/on-rails solutions because there is typically hell to be paid as soon as you venture slightly off of the rails. If not, they also tend to have an overabundance of features; leading to slowness or a fertile ground for vulnerabilities.
> High-level DB migrations
Having used Datadude[1] I can say for certain that there are few approaches worse than migrations. The problem is that, once you are stuck with a turn-key framework, you are completely stuck with their approach (which is usually horribly archaic).
Unbundling all of these things might require more work up-front, but can result in significantly improved productivity in the long run.
[1]: https://www.sqlshack.com/working-with-database-projects/ https://www.sqlshack.com/working-with-database-projects/
- Winsaucerer 4y ago> People can be wary of these bolts-included/on-rails solutions because there is typically hell to be paid as soon as you venture slightly off of the rails This is so very often the case, and you often can't tell in advance before you use the framework or library or whatever. You just have to use it, and get to a certain point of maturity in your project before you discover these limits.