Let's face it...as developers we're expected to know a lot of stuff about a lot of things: Database design, application design, numerous languages and constructs, testing, debugging, etc.  I don't know about you guys, but my head can only hold so much information before an implosion is imminent.  Do yourself a favor and make buddies with a DBA near you (in my case, a guy 2 cubes over).  More than likely they've devoted their entire careers to RBDMS of numerous varieties, and chances are even better that they know a few things that you don't about databases and how to squeeze out some extra performance from that slow running query you can't seem to get running quick enough, etc.

I've always kind of envied the hard core database guys.  It's not a job I'd want on a daily basis...too much stress for the big dogs, but most of the ones I've worked with always have a certain air of calm and tranquility about them.  The ERM server could be on fire right down the hall, and they're as calm as Hindu cows.  As they should be...a company's database(s) are their heart and soul, their bread and butter.  An application is worthless without a decently running DB behind it.

I've made friends with one of ours, and already I'm learning tons that either A) I didn't know or B) had forgotten after a couple of years of being on my own.  Another thing I've found with these guys is that it either is or is not...there isn't much gray area when it comes to why things should be done a certain way.  That kind of finality is a refreshing change coming from an environment where there's a dozen ways to do one thing, with most of them being no more right or wrong than the next option.

Share this post: | | | | |