4 ms·
Not in my experience though our DBA was very good (oh my first boss was Dijkstra he mentioned down the pub one lunch time) And would you not have your IDE on o
by walshemj 9y ago
Not in my experience though our DBA was very good (oh my first boss was Dijkstra he mentioned down the pub one lunch time)
And would you not have your IDE on one monitor and your SQL IDE in another so you could look at both sets of code.
- scarface74 9y agoUsually with most modern automated deployments, you keep your build artifacts in a package (zip file, tar, etc.) and run a script to deploy it to your target system. Rolling back is a simple matter of installing the previous archive. That doesn't just apply to code anymore. You can treat "infrastructure as code" also. You can do A/B upgrades, rollbacks, etc. There is so much better tooling around regular code than sql/stored procedures. How many times have you seen stored procedures with hundreds of lines, duplicated stored procedures with V1,V2, etc appended to it, commented out logic etc? I've had to wade through some hairy code to but at least with a code, I can do some automated guaranteed safe refactoring, find dependencies, keep the interfaces backwards compatible, etc.
- walshemj 9y agoSounds like you have been working at companies with poor procedures and employees without the required skills. Avoiding SQL in favour of an ORM or inline sql is 95% of the time a sign of laziness.
- scarface74 9y agoYou did see me preach about all of the capabilities for unit testing without a database dependency, type safety, flexibility (with Linq I can switch back and forth between an RDMS and NoSql without any code changes)?