5 Things Every DBA Needs To Say To A Developer

In case your iCal stopped working with the new iOS update I feel the need to tell you that next week is Christmas here in the USA. I assume it is Christmas in other parts of the world but I’ve never witnessed such celebrations personally in other countries. And I hate assuming that the rest of the world follows what we do here in America. That would just be rude.

Being that is Christmas it seems fitting to show a kinder, gentler side of yourself to those around you. To that end I’ve put together a list of five things that every DBA should say to the nearest developer.

You’re welcome.

I was wrong

I know what you are thinking, a DBA is never wrong. But that’s wrong, which makes this an odd double negative that shows how you are right. Rather than head down that path let’s just agree that a little humility is not a bad thing no matter how important you think you are. If you were wrong, or the developer was right, tell them. The worst case scenario here is that you build some trust among team members.

I don’t know, but I will find out

No one person knows everything. I don’t care what you’ve been told by some fancy piece of marketing. We all make mistakes. We don’t know everything. What’s the harm in admitting this to a developer? Do you think they will attack you like a shark in blood soaked water? Admit you don’t know something, promise them to do the research, and then come back with an answer even if the answer shows that you would have been wrong.

It depends on…

One of the running jokes I see is the use of the phrase “it depends”. I call it a joke because I see people rely on this tactic many times without any real knowledge to back up *why* it depends. If it depends, then tell the developer what it depends upon. Outline for them the pros and cons. Detail the costs, benefits, and risks. Oh…and if you don’t know them…see my previous point.

Yes

Because we are often saying “no”. Throw them a curveball every now and then and just say “yes” to something. Even if they ask for the database to be colored blue. Just say “yes” and “this is what it will take” and see what happens. They might not be able to give you what it will take. But then they would be the ones saying “no”, and not you.

Thank You

Because it’s good manners and because, like yourself, not many people take the time to thank people for their efforts. How many times have you been thanked for backups running perfectly? Never. Well, why not thank the developers for their batch process running perfectly because of how it was coded? Would it kill you to be nice for a change?

I bet if you made an effort to say these five things at least once a week to any member of the development team you support you will find your relationship growing stronger with each passing week.

Next week is Christmas. Not a bad time of the year to be good.