Download the authoritative guide: Cloud Computing 2018: Using the Cloud to Transform Your Business
This matter-of-fact announcement came from Joni, one of my slightly buzzed developer teammates, as we enjoyed a Thursday happy hour around a crowded table, drinking beer and eating munchies. Having just graduated and barely settled into my first job, it was no surprise Id never heard the phrase mental health day.
In my head I pictured her going to visit some kind of therapist because the job is stressing her out. Id heard the term going mental before and that wasnt a pretty picture. So maybe she was about to burst from all the looming deadlines.
Being the green guy at the table, I naively asked, Are you going to see some kind of doctor?
More intrigued, I asked, Are we allowed to do that? I mean using a paid sick day for you know not really being sick?
Ah, but I am sick sick of work! Besides, who is going to know the difference? she responded with incredulity.
Now I was the one who was incredulous. The entire team was under a steep learning curve with a new ERP module we were customizing. We were way behind on the project schedule and Joni was the defacto team leader because she was the only one experienced with this module.
But Joni we have a package due for QA testing Monday and we are way behind. Arent you planning on working this weekend like the rest of us? I said.
She quickly shot back, That answer would be N-O no! My code is working just fine.
One of my other teammates, Doug, piped up with some initial sarcasm. Well, bully for you Joni. Of course youre done youre the big expert with this module. But how do you know your code will work with all of our code once integrated for QA testing?
Not my problem Dougie, she said. And she knew Doug hated to be called Dougie.
As Doug grew hotter under the collar, I jumped back in. But it should be your problem Joni because we may need your help this weekend. And shouldnt we run some tests with all our code before submitting to QA Monday?
Joni retorted, Integration testing is their responsibility, not mine. If something doesnt work because you guys have mistakes in your code, then well figure that out next week when QA kicks it back.
This was too much for Doug. His raised voice made everyone at the table focus on the banter.
Youre being selfish Joni. While you are enjoying your mental health day, well be working hard to make up time. And how do you know there wont be problems caused by your code?
Thats easy. Because I know what Im doing and you guys are just trying to keep up, she said with a wry grin.
This was typical Joni behavior. She had a major superiority complex. There was no doubt she was good and very experienced, but she did very little to share that experience to mentor others.
Her idea of success was focused on her own work, not the teams. So in her mind, if her code was done, then she was entitled to take a day off to free her mind.
If we had a more well-defined development process, then Doug and I may have had a case. But the fact was that individual accomplishments and heroics were promoted more than teamwork.
Joni announced to the table, Look, to be at the top of my game, I need to take a well deserved break now and then. Maybe if more of you took a mental health day to clear your heads and relax, wed all be more productive.
I for one am 100% positive that I produce more quality code after taking a mental health day. She paused and looked at Doug, then nonchalantly stated, Then again, maybe it wouldnt help Dougie.
I wont repeat what Doug said as he put some cash on the table and stomped out of the bar. Joni just smirked and downed her beer.
Following Suit (Or Trying To)The next morning I walked past Jonis empty cube and shook my head. Then I noticed another empty cube. Doug hadnt shown up yet.
Our manager Jim leaned into my cube and asked, Any idea where Doug is?
I replied Nope. I noticed Joni wasnt in either.
Jim replied, Yeah, I dont know where either one is today. He walked into his adjacent office and his phone rang.
I quickly determined it was Joni. The conversation on Jims end went something like this:
Oh, you arent feeling well? Your code is ready for Monday right? Oh good. Well rest up and enjoy your weekend. He couldnt have sounded more cheery and empathetic.
Then his phone rang again. The tone in Jims voice took a decided turn for the worse. It was clear Doug was calling in sick. Jim was giving him the third degree with questions like - How sick are you? Do you have a fever? Are you going to the doctor?
I heard Jim tell Doug that if he knows what is best, he better get his rear in the office and complete his assignment.
As soon as he hung up, I called Doug.
Dude, are you really sick? I asked.
He responded, Of course not. I am taking my mental health day, just like Joni. Why should I be working my butt off while shes out shopping?!
I could certainly empathize. But the fact was that Jonis assignment was done based on our managers expectations, even if it ended up not working once integrated. And it was also a fact that Doug hadnt made it that far with his code.
Doug, if you dont come in, I think Jim is going to be ticked. You dont want to get fired, do you?
After a brief pause, he said, Its not fair. I mean it will take us twice as long without her in the office and the deliverable will be late anyway, so what is another day?
I hear you man. But what will that accomplish except making you look bad and ticking off the rest of the team? You may feel good for one day, but I bet youll not enjoy your day off because you have a conscience and you care about the success of the team -- unlike Joni.
I could hear his resigned sigh through the phone. And sure enough he came in later that morning.
We all worked through the weekend and figured things out together, even without Miss know-it-all. And the integration testing went just fine.
Doug asked me, Does it make me a bad person that I was secretly hoping for Jonis code to cause a problem?
I laughed. Then we can be bad people together, I said. Maybe wed feel better after a mental health day!