I don’t think so.
What if they were abducted by aliens? Would no other developer left on earth be able to complete a root cause analysis and fix the problem?
The fact is that it is usually not the fault of the developer on vacation if a problem arises that can’t be fixed. There should be processes in place as part of the development and implementation process to ensure code is tested, walked through, and documented.
If knowledge transfer isn’t baked into the process to educate the support team, developer peers and users, then you end up with unnecessary and annoying phone calls on vacation.
Why not keep the phone and simply leave the laptop at home? I know I felt pressure to bring the laptop with me on vacation. Even if your manager says to disconnect while on vacation, there is always a nagging feeling in the back of your mind that it will reflect poorly if you do not bring it and something goes wrong.
For many developers, a vacation also means a chance to play around with technology. Evaluating new gadgets, software and development concepts are actually fun to true techies. And it’s becoming more common to be writing code on your tablet because it’s an all-in-one device where work and pleasure can’t be easily separated.
Plus, in the difficult economy of the last few years, you don’t want to let your guard down and seem less committed than your teammates. If they are all staying connected on vacation, you feel indirect pressure from your peers as well to improve your job security.
I have found as a manager that it is up to me to set the tone. This is more than making sure processes are in place, it is also building a culture of accountability. When one developer goes on vacation, it is expected that their team members will cover for them. The team (in theory) has the confidence in the established processes so that they know they can solve problems without disturbing their teammate’s time off.
The hardest part for me is walking the walk – not checking in while on vacation. I have to also put trust in the system and my team.
Remember when I told my wife I’d be back in about an hour? Do you think that was a true statement? Even when I said it I had my doubts. Once you get sucked back in, you may find yourself going deeper and deeper down the rat hole. Before I knew it, hours had passed and the problem was still not fixed.
Working on the Beach?
I had a brilliant idea. Just take the laptop down to the beach! Although the beach didn’t make my list of coding happy places, as long as I had battery power, I could use my local test environment to keep troubleshooting. And I was sure she would be thrilled to see me.
Back then it seemed like a good idea. But now that I have been married 20 years, I realize how ridiculous that idea was.
As I kicked off my sandals, laid back and fired up the laptop, my wife stood up and started packing up her stuff.
“Where are you going?”
“I am going somewhere I don’t have to look at you doing work when you should instead be paying attention to me and enjoying your vacation.”
I was mad. I mean, I was just doing my job, right? How selfish of her!
What I have learned is that I was the one being selfish. Life requires balance and the world will not end if I take a week of vacation.
I also learned that sand and laptops are not a great combination.
Next vacation, the laptop stayed home and the cell phone was mostly turned off. My attention was fully where it should be – enjoying the sights and sounds of the beach, spending time with my family and reading “XML For Dummies.”
Ahhhh! True bliss!