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.
Panic, Chaos, Destruction. My work here is done.
Drink. Get drunk. Fall over - P O'H
OK, I will win to day or my name isn't Ethel Crudacre! - DDEthel Crudacre
I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer
Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
I've always been the type of guy that doesn't care what my co-workers / team mates are doing because it doesn't affect me one bit. If the project fails because of them, thats on them, not me. If the boss comes and asks me why my piece isn't done or whatever, I just usually say I'm waiting on Bob to finish his piece and I've been asking him for it for 2 weeks. I usually say it with a slightly sarcastic tone and let the boss worry about getting through to Bob. I'll usually just bug Bob for a week or so before giving up and figure he doesn't want to do his job for whatever reason.
So on my current project, I've got a Bob. Bob is responsible for the web site and the database and database layer and he used to be responsible for the WCF service, but he is so completely worthless, I just took it myself and did it.
1 month ago I asked Bob to finalize out ObjectA and ObjectB. ObjectA is basically a single table. ObjectB is more complex and probably involves ~5 or so tables. First time I asked him for it, I got "Oh,I can't work on it now, they are changing the specs all the time, I'm waiting for the final specs". This was complete BS as both objects were 90%+ defined by the business unit.
A couple of weeks later, Bob got the official specs and still hasn't done it. He (at the time) was responsible for the WCF service. I built it and stubbed it out for him. All he had to do was drop in a single line of code. return databaseLayer.GetObjectA(); After a week, I finally get an IM saying he checked in the code and he tested it briefly with the WCF test client and it looked to be working.
LMFAO... REALLY? You tested it in the WCF test client? REALLY? You mean the one that comes with Visual Studio?? REALLY? I was in disbelief, but I didn't say anything at the time cuz I got better things to do then argue with worthless co-workers.
How exactly did he test it with the WCF test client?
1) the project I sent him was a console app in debug mode and a service in release mode... he had somehow jacked up the project setting and made it a windows app. Wouldn't even run if he tried.
2) the service was self hosted to support SSL & REST. Last time I checked, the WCF test client doesn't support either. It only supports http/wsdl.
Holy crap. So now I just think he is a complete BSer who never does crap. To this day, I still have not gotten ObjectA and ObjectB.
I mention it every day in the scrum meetings that I haven't gotten it yet and they are blocking items, but the PM doesn't seem to care, she just jots it down. Lol.
I agree with you, it just happens in every company. You may find one or two in a company which you work with.
There are only 2 options for you now.
1. Just switch the company where you are working and join some other company. However don't keep much expectations.
2. Don't bother about that poor guy, Though the biggest mistake you have done is work on his code part. I agree you could have helped him to some extent but don't ever make a habit of working on some one else code completely.
Yeah, I know doing his job for him is just enabling him... but I have ZERO interest in working evenings and weekends because of his crap. I'm thinking I'm just going to have a talk with the boss tommorow in case he doesn't know whats going on.
Also next time you never forget to keep your manger in loop through email when ever you are asking him about the work done. I have seen while working with out mates we become close friends and mostly discuss in formally and when it comes to the end of the day all that is required is the formal communication that has happened through emails/chat/groups etc else the manager will not come to know what;s really going on.
Really surprises me about your manager not much bothering about when you say something in your daily scrum meetings
Discuss it privately with your manager/scrum master/whatever. You can be sure that he is putting his point of view across to them, and that he will be assigning blame to (i.e. sticking knives in the backs of) others, to cover his @rse, and one of those he's blaming will be you.
If he does that, and you do nothing to counter it, people will believe him, and you'll get the blame.
And make sure that he's not telling everyone that you're difficult to work with. That's a usual tactic that's employed by the incompetent, and, again, if no-one says anything to counter it, it will be believed.
I wanna be a eunuchs developer! Pass me a bread knife!
And make sure that he's not telling everyone that you're difficult to work with
If it gets to that stage it is time to move on, thankfully, as a contractor, I only had to put up with that sort of crap short term. Only once have I packed up my bat and ball and gone elsewhere to play!
Never underestimate the power of human stupidity