When Developers Drink On The Job

When a developer drinks or does drugs on the job, there’s a right way and a wrong way to deal with it.


How to Help Your Business Become an AI Early Adopter


(Page 1 of 2)

"Is that alcohol I smell on your breath?"

The question seemed to hang in the air for a very long time, even though we both already knew the answer. I had been suspicious that one of my best developers had an alcohol problem for quite some time.

But this time the stench made me finally address the issue, something I should have done long before.

Let me take a step back and provide some history as to how this situation came to a head. Tim was one of the most liked developers in the company. He had been there from the beginning, one of the first few employees to take the risk and successfully launch the company.

Tim wrote much of the code for the original product and his code was still present years later. His code was legendary. But if you have ever had to troubleshoot or build upon the original code that was created in a startup, you understand that “legendary” doesn’t always mean quality.

Some of the code was extremely innovative and some of it was a mess. And come to think of it, this was what life was like working with Tim.

He was a great problem solver, yet thanks to alcohol, he was also a mess. But the mess was not obvious, which made this a tricky situation.

I was hired in to lead the team and inherited Tim. It seemed odd to me that one of the original founders was still a developer and not in some leadership capacity.

But then again, some people just want to code and not have other responsibilities, so it wasn’t shocking. When I first met Tim, he didn’t say much. He was nice and all, but just kept conversations brief.

In conversations with those who had worked at the firm for a while, I found out that Tim had bounced around to a few teams. Again, I couldn’t figure out why one of the original developers couldn’t find a home and ended up on the consulting team. I would have expected him to be writing core product code.

Whenever I asked someone about Tim the main response was “He is such a nice guy.” or “What a good guy.” So I figured he must be a quiet, affable genius and that I should count my lucky stars he was on my team.

Then the cracks started to expose the mess under his nice, smart-guy façade. He would show up to work later and later, with no notice to me or anyone else. His office door would be closed for hours, for no known reason.

I also noticed how bloodshot his eyes were. I once asked him if everything was okay because his eyes looked so bad. His response? “I have really bad dust allergies.”

So I asked the cleaning crew to give Tim’s office a good scrub down. But his eyes continued to have a red tint and I never noticed any sneezing fits or sniffles.

I should also mention that Tim was ALWAYS chewing gum. And his breath always smelled like strong spearmint.

The other thing that threw me off was that customers loved Tim. He was so knowledgeable about the product and he was a subject matter expert, even more so than the customer in many cases. And no one was complaining about his work or his behavior, so I wasn’t concerned.

Because of his founder status at the company, I ignored these warning signs. I shouldn’t have.

Then one day I received a phone call from one of our partners who was working with Tim at a customer site. They said that Tim wasn’t showing up to work on time and that his deliverables were slipping. Even they were surprised, because like everyone else, they liked Tim and respected his knowledge.

When I confronted Tim about it, he said he hadn’t been feeling well and apologized. Said he would be fine and that the deliverables weren’t really in jeopardy. I had no reason to doubt him. Well, in retrospect, maybe I did. Anyway, I didn’t make a big deal out of it and he did make the deliverable on time.

Then a few days later when back at the office, Tim disappeared in the middle of the day. No one could reach him and he didn’t tell anyone where he was going. Then around 4 PM I passed his office and saw the door was shut. I knocked and Tim opened the door.

Next Page: the confrontation

Page 1 of 2

1 2
Next Page

Tags: developers, IT, careers

0 Comments (click to add your comment)
Comment and Contribute


(Maximum characters: 1200). You have characters left.



IT Management Daily
Don't miss an article. Subscribe to our newsletter below.

By submitting your information, you agree that datamation.com may send you Datamation offers via email, phone and text message, as well as email offers about other products and services that Datamation believes may be of interest to you. Datamation will process your information in accordance with the Quinstreet Privacy Policy.