By now you've hopefully heard about craftsmanship over crap and the other day I heard about a research report where they concluded that university students majoring in engineering have problems translating theory into practice (article in Swedish). Education is not the key to becoming a good programmer. It is a catalyst that will help you get better faster. But it will always take time to become a good developer. But to become a great developer you must never stop learning. So why am I talking about this? Well, it's because something I read that made me real sad:
"Benefits: [...] Through less lines of code you can get more done."
And this is not the only example from the DBA world I've seen. First of all the statement is false. Through less lines of code you get the same work done. But less is not more. Just reducing the number of code lines for the sake of reducing lines generally result in code more difficult to understand and maintain. For some reason being a DBA and being a developer seams like a rare combination. I've worked with a few DBAs that worked like developers mainly because they were developers that had an interest in databases and then turned into DBAs. And what do I mean with "working as a developer"? Being lazy, i.e. automating as much as possible and making sure they can reuse stuff without duplicating code. Maybe even having a number of automated tests. And having at least basic understanding of what makes code easy to understand and easy to maintain.