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 doesnt 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 wasnt shocking. When I first met Tim, he didnt 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 couldnt figure out why one of the original developers couldnt 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 Tims 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 wasnt concerned.
Because of his founder status at the company, I ignored these warning signs. I shouldnt 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 wasnt 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 hadnt been feeling well and apologized. Said he would be fine and that the deliverables werent really in jeopardy. I had no reason to doubt him. Well, in retrospect, maybe I did. Anyway, I didnt 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 didnt 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.
One of the ways around the issues of security and control that make some businesses wary of cloud computing is to build a private cloud -- one that remains within the corporate firewall and is wholly controlled internally. Private clouds also increase the agility of IT an organization's IT infrastructure and make it easier to roll out new technology projects. Download this eBook to get the facts behind the private cloud and learn how your organization can get started.