Episodes / Episode 9 of 9
DBA Burnout: Work Fewer Hours, Get More Done
The four causes of DBA burnout, a trench story about dehumanization, and the schedule that gets more done in 11 focused hours than most DBAs get done in 60.
Watch on YouTubeFull course playlistSubscribe
In this episode
- Over achieving, and why working hard isn’t worth it
- Dehumanization, and a DBA trench story: 40 hours a week of email updates
- Self-care: food, sleep and exercise are part of your job
- Attention management: the 11-hour week for new DBAs, and building up to 3 focused hours
Chapters
Transcript
Read the full transcript
Over achieving
Let’s talk about Burn Out. The first major cause of burn out, over achieving.
Working hard isn’t worth it. An over achieving employee typically costs more money from the drama they cause with other team members than what they bring in from their extra productivity. Those same over achieving employees will often quit when the recognition doesn’t match the effort. You are more valuable if you keep yourself part of the team and from being driven to quit. A sign that you’re over achieving is when you can sense that your peers are rooting for you to fail.
Dehumanization
The second major cause of burn out is dehumanization.
Every company I’ve worked for and every team I’ve been part of always has a problem with seeing DBAs as machines. This dehumanization puts unrealistic workloads that will drive anyone to quit. Working remotely significantly increases this phenomenon. It’s a constant battle to try to remind the people that you work with that you are in fact a human.
It’s time for a DBA trench story. I once supported an application that had significant time to market pressure to get it live. The pressure was so high, that no developer time was allocated to create tooling to modify customer email addresses. After the app went live, requests to change customer email addresses started pouring in. As a workaround, a process was set up to have DBAs run update scripts to make the changes. How many update script runs did this require? At first, enough to eat up about 2 hours of a DBA’s time a day. As the app grew in popularity, the amount of time required to update email addresses increased. The developers’ time was too important to use up to solve this problem. This went on for two years until those script runs took up 40 hours a week. At that point, I said if we onboard any new customers, we will need to hire a new DBA just to do these script runs. It was at that point that a developer was tasked to solve this issue. It took a developer working one day one time to modify the web GUI to allow the customers to update their own email address.
Fighting that type of dehumanization is a constant battle. You will most likely lose. You have to small talk, and pretend to be extra human to fight it. Best I’ve come up with is keeping a running list of priorities that I’m working on. When leadership asks me to take on some inhumane task, I tell them I can but x number of these other things won’t happen. Which ones do we need to focus on more?
Self-care
A third thing that we need to talk about is self-care.
DBAing is a brain job. Your brain needs things. It needs a good diet. It needs a good night’s sleep. It needs exercise. If you haven’t tried these things before, you may have heard they make a slight barely measurable increase in your ability to think, feel good, and have energy. This is a lie, and complete dodo. In reality, do these things, they make a thousand times improvement on your ability to think, feel good, and have energy. Eat like a Mediterranean, sleep all night, and exercise for an hour 3 to 5 times a week, it’s part of your job.
Attention management
A fourth contributor to burn out is attention management.
There is a fundamental difference between working and getting work done. Many DBAs make this mistake, and when they fall behind on objectives, they try to put in more hours to get them done. To the surprise of no one, this does not help. It does impact your work-life balance, contributing to burn out. How many hours should you work in a week then? The answer is 27.
To be honest, 27 is for seasoned senior database administrators only. Starting out, try for 11. If you can do those 11 hours my way, you will likely make more progress on objectives than any of your 60 hour work weeks. For the entry level DBA here is what I want your week to look like.
Monday to Thursday. 8:00 AM ish. Turn computer on. Get logged in. Open up your apps. Go get coffee. Eat small breakfast or snack. Look longingly out the window. Take poopy. 9:00 AM. This part of the day is for looking at things and scheduling things, not doing things. Go through your daily checklist of things to look at, if you find things that need changed, schedule them starting at 1:00 PM. Read and respond to emails, Teams, and texts.
10:00 AM. Watch YouTube, TikTok, take a nap, play Minecraft. 11:00 AM. Lunch. 1:00 PM ish. Ignore all new emails, Teams, and texts. Start doing the things on your things to do list. Do them one at a time (you can’t multi-task, not even a little).
2:00 PM Go watch TV or something, we all know you’re not doing any more work today. 4:00 PM Go to gym, move heavy things around just to leave them where you found them.
Friday. 8:00 AM ish, same as Monday. 9:00 AM, same as Monday, but schedule changes starting at 1:00 PM ON MONDAY. Don’t make changes on Friday afternoon that will undoubtedly break over the weekend. 10:00 and 11:00, same as Monday. 2:00 PM.
Learn something. Teach something. Confirm your thoughts on what current industry standard best practices are. Try to figure out what’s coming next, but don’t fall for the hype.
If I had an entry level DBA that put 11 hours of work in like that for me, I would be amazed and so grateful. After you get to where you can do 11 hours, slowly increase your 9:00 AM and 1:00 PM sessions until you can actually do attentive work for 3 hours. I’ve never met someone who could do more than 3 hours, and Google and ChatGPT agree that they don’t exist. If you see one, run. They are not human.
