|
| Featured Contents |
| Question of the Day |
| The Voice of the DBA |
Communication, For Incidents and Life Many years ago, I was on call for a production system. This was common for me since I was one of several production DBA’s for the company. It was a normal weekend for me, and I got up and started playing with my kids. They were heavily into trains, and we were laying out our latest large train set in the living room. We would cover most of the floor with train tracks. The kids would later use the train to pick up little people from various cities, and they played various games. As I assembled the tracks, I got a message on my phone. “Sys alert: DB-01 Server is not responding” Since this was one of the primary databases, I was very concerned. This was the days before Slack, so we didn’t have good “channels” to post a message and ask what was going on. I logged in and started troubleshooting to figure out what was going on. At the same time, I started reaching out to some of the operations folks to see if they knew anything. I got a response back. Ops: “Hey Pat, we took that down since we are doing upgrades on the system right now; it should be done soon”. Obviously, my first thought was WTF????? But….Instead. Me: “Ok, I wasn’t aware of this. Do you need anything from me?” Ops: “No, we should be done in about 20 minutes, and then you will probably need to validate” Me: “Ok, I’ll wait and see” 20 minutes later, Kids: “Dad, dad, dad, can you finish the train tracks…” Me: “A few more minutes, I’ll help soon” 30 minutes past……. Kids: “Dad! Dad, Dad!......can we get the train tracks finished” Me: “Almost done…..just a few more minutes” Me: “Hey guys, still waiting here by the computer. Do we have things back up and running” Ops: “Oh ya, all good. We were done about 30 minutes ago”........... Some of you out there will be nodding your heads right now since you lived through days like this as well. Anyone who’s been on call for a system has dealt with issues when the system goes down or problems arise. It’s especially hard when simple communication issues make you lose time with family, friends, or just relaxation. To help, I thought I would share some simple communication tips and tricks. Now keep in mind, technical folks like engineers, operations, database people, and network people are NOT typically great at communication. They are usually very introverted, and the last thing they want is to talk about something that might cause downtime or a problem in the system. These guidelines help with that.
I know these all sound like communication tips for incidents and system updates, but they're really guidelines for all the communication you do. You can use these in meetings, when working with other teams, or even when organizing things with friends. The more you practice these ideas of clear communication, the better things will be for you in your career. Hope these help, and you have uneventful weekends, spending time doing the things you love!
Pat Wright Join the debate, and respond to today's editorial on the forums |
| Featured Contents |
