In my effort to help build bridges between various groups inside of IT departments I decided to come up with a handy guide for developers to help them communicate better with their database administrators. At the very least I am hoping to reduce the number of times staplers are being thrown during a code review.
Enjoy!
I think you forgot one (the “how to bribe a DBA):
Dangerous: Here is a Beginning SQL book.
Safer: Here is an In-depth SQL book.
Safest:Here is a subscription to Safari Books online.
Ultra Safe: Here is a pound of bacon.
Nice!
Don’t you also need a “speak slower, use smaller words” guidance, too? [ducking]
Yes, DBAs should speak slower and use smaller words when speaking to developers and architects, I completely agree with you.
I see what you did there….
Developers don’t respect DBAs. They just think of them as an unnecessary obstacle. They also tend to think of the database as the crud operator for their object oriented diarrhea.
I’m not sure I would say that is true for all developers, but I would say that people tend to blame things they don’t understand. WHich is often why devs and DBAs stand there, pointing the finger at each other.
Ha! I have certainly looked many a developer in the eye and asked “why do you want to treat our very expensive server as a flat file”?
Eric,
It’s because the data is stored in files, that’s why. I can’t think of any other reason.
Yes, you are correct.
Very true and interesting … I will have Developers read it first before talking to me … lol ..