The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Umm... why *should* I care about what somebody else does? I'm going to stress out about what my co-workers do??? Lol. Do you? Are you one of those co-workers who goes to your manager and reports your co-workers for only working 7 hours and 45 minutes per day when you are working 10 hours? Do you report your co-workers for standing around their cubicles chatting about the game when you are sweating it out implementing code?
I'm not Bob's boss, nor am I his mother, his parole officer, his wife, his therapist, etc. Not my job to care about what he does or why.
If Bob is not cutting it because he doesn't like his job, that sounds like Bob's problem. And Bob's boss's problem.
If Bob asked me for help, or had a ton of stuff to do or whatever, then I would probably feel different. However, its obviously Bob is a worthless piece of crap who BSes people and is an outright liar.
Really? He tested a REST/SSL service with the WCF Test Client? Lolz. What a waste of DNA.
You need to talk to your team lead and functional manager, to verify they are aware that Bob is a problem. They may have been working on Bob for weeks, counseling him, giving him that, "Are you happy working here?" talk, writing him up preparatory to letting him go. Don't assume that they don't know that Bob is a problem. If they know, they have probably already mentally compensated for his drag on the schedule.
You also need to be sure they know you have been bringing up this issue. I once had a manager who, it turned out, never read more than the first couple of lines of any email. So my detailed reports describing exactly why we were gradually sinking had totally escaped his notice. With some managers you pretty much need to grab them by the lapels and shake them into wakefulness. Then they massively overreact of course, firing Bob on the spot and also the whole rest of the team, and everyone else in the company who looks like they might do software. So careful what you wish for.
I also second the recommendation about finding a new employer if your current employer tolerates Bob.
Yeah, I used to work with a guy everyone called 80% Rob. He'd do 80% of the work, declare victory and move on. He was one of those guys who was grooming himself to be a manager. He'd wear the white shirt and red "power" tie, as well as red suspenders. He would position himself as a facilitator, meaning he didn't have to do the work, but made sure he was the one with you when you handed in your work so it looked like he helped. If he was good, he'd convince you to give him the material so he could hand it in for you and let you get back to your work. I fell for that trap once, the work I gave him involved three files, he handed in only two. I made accidental enemies because they came at me claiming I hadn't done the work. It took about a half hour to convince them I had done the work, while they insisted I had screwed up. When I confronted him about it later he said, "Somebody dropped the ball." He couldn't bring himself to admit he was the one that did it.
I had another one give me a component my project needed that he insisted he had tested and then went on a two week vacation. His code GPFed immediately, not after using it or stressing it, but immediately. We were on a tight schedule so I dived in and cleaned up the POS. I think I gutted over a third of the code that was redundant and/or non-functional. In the end, I kept only subroutine that worked, in the most retarded manner possible, just so I could point to it and say, this is his usual programming style. Wanna know what it was? A routine to center a message on the screen (back in text display days). Did he take the length of the line, subtract the length of the string to print, and then divide that by two, so he would know how many spaces to print before printing the string? No, that would have been too easy and too fast. Instead he filled a buffer the length of the line with spaces and placed the string at the beginning of the buffer. He would then count the number of spaces in front of the string and the number of spaces after the string. If the leading count was less than the trailing spaces, he would move the string one byte over, add a space at the beginning and start again, finally finishing when the number of leading spaces was equal to or greater than the number of trailing spaces. I'm sorry to say that code was almost sensible compared to the code in the rest of the application that consultants had spent six years writing. The company had finally figured out it was being taken for a ride and assembled an in house staff to do the clean up. When he got back from vacation I grabbed him and started taking him through the changes I had made and he looked at it and said, "Yeah, that's my code." I fumed thinking this idiot couldn't even recognize how or even that it had been changed. I advised him to take a tube of KY jelly with him when he went to so our manager because he was going to be reamed for handing me the POS.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
Sh*t happens, but unless your job depends on Bob completing his tasks, then i would just keep pointing the problem Bob is in every meeting, otherwise, i will go straight to my boss (or his) so he/she make his work and slap Bob in the head.