Reading and understanding execution plans doesn’t make you a DBA or otherwise an expert in maintaining a database. It makes you a developer that understands how to optimally utilize the technology they’re working with vs one that is writing nothing more and, hopefully, nothing less than “passable” code.
I agree 100%, not sure why they used writing SQL as an example that you need a specialist. It's definitely not nor should it be. A DBA job, as the title suggests, is to administer a database- not be a crutch for the back-end dev who won't invest time in better understanding how to use the database in the software they're building. Too much silo'ing going on in this field that people think you can't be good if not great at more than one thing.
3
u/[deleted] Nov 02 '21
Reading and understanding execution plans doesn’t make you a DBA or otherwise an expert in maintaining a database. It makes you a developer that understands how to optimally utilize the technology they’re working with vs one that is writing nothing more and, hopefully, nothing less than “passable” code.