Holy CRAP -- worst co-worker ever...
-
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. Lo
-
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. Lo
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. Thanks,
Ranjan.D
-
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. Thanks,
Ranjan.D
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.
-
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.
Yeah that would be great! 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 Thanks,
Ranjan.D
-
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. Lo
Pretty bad, but does Bob pass gas, releasing an unpleasant odor in the office 9 times per day? http://www.codeproject.com/Messages/4469998/Wow-Now-This-Is-Just-WTF.aspx[^] X| Soren Madsen
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
-
Pretty bad, but does Bob pass gas, releasing an unpleasant odor in the office 9 times per day? http://www.codeproject.com/Messages/4469998/Wow-Now-This-Is-Just-WTF.aspx[^] X| Soren Madsen
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
Some of us are old. We can't help it. :sigh:
-
Some of us are old. We can't help it. :sigh:
-
I feel like making a cow joke with reference to your profile image, but I don't want to offend any members on the site. Soren
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
Bull. :-D
-
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. Lo
May be he is suited as "Bob the Builder" job not developer job ;)
-
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. Lo
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!
-
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!
Mark_Wallace wrote:
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 RAH
-
Mark_Wallace wrote:
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 RAH
I like to kick the @rses that offend me, before moving on.
I wanna be a eunuchs developer! Pass me a bread knife!
-
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. Lo
SledgeHammer01 wrote:
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.
So we've learnt you've always been the type of guy that doesn't care what your co-workers / team mates are doing as long as it doesn't affect you one bit.
-
SledgeHammer01 wrote:
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.
So we've learnt you've always been the type of guy that doesn't care what your co-workers / team mates are doing as long as it doesn't affect you one bit.
That was exactly what was going through my mind +5
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
-
Pretty bad, but does Bob pass gas, releasing an unpleasant odor in the office 9 times per day? http://www.codeproject.com/Messages/4469998/Wow-Now-This-Is-Just-WTF.aspx[^] X| Soren Madsen
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
-
SledgeHammer01 wrote:
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.
So we've learnt you've always been the type of guy that doesn't care what your co-workers / team mates are doing as long as it doesn't affect you one bit.
-
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. Lo
That's Bob for you. I've had my fair share of them but none half as kak as yours. I had a total prick of a project manager once. He was forced to take over our projects but it was clear he had no interest in us. Eventually, he thought it would be a good idea to arrange a team-bonding night out which nobody really wanted to do, with him at least. He decided that we'd go to the dog-racing in Brighton and eat there. He said the company's contribution was £20. Someone asked if that was £20 per head or £20 in total. If the latter we could buy a pizza and a 2 liter bottle of Coke from Lidl and heat it up in the microwave at work and then have a team hug afterwards. The tosser said, of course it was £20 per head. Like, wake up you useless prick, the guy was only kidding. The project manager's name was not Bob, but he was a waste of space all the same.
"I do not have to forgive my enemies, I have had them all shot." — Ramón Maria Narváez (1800-68). "I don't need to shoot my enemies, I don't have any." - Me (2012).
-
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. Lo
You need to send him a fart bomb.
If your actions inspire others to dream more, learn more, do more and become more, you are a leader.-John Q. Adams
You must accept one of two basic premises: Either we are alone in the universe, or we are not alone in the universe. And either way, the implications are staggering.-Wernher von Braun
Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.-Albert Einstein -
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. Lo
SledgeHammer01 wrote:
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,
Have you ever thought that perhaps it is you that is the problem? With an attitude like that, I expect you bring out the worst in people. This is why you find yourself surrounded by Bobs! I would recommend two things: Firstly, you either start to become a better team-player, or become an independent developer. Stay at home, work from your garage, choose solitude! Secondly, if you do encounter an under-performer at work, don't ignore it, don't bitch about it on forums. Do something about it! If, after you have tried to help, they just can't cut it, politely inform your manager. They might have personal issues that you are unaware of, or, they might not like their job, or ... all sorts of things might be affecting their performance. Who knows, one day you might be the 'Bob'. Regards, Colin E.
-
SledgeHammer01 wrote:
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,
Have you ever thought that perhaps it is you that is the problem? With an attitude like that, I expect you bring out the worst in people. This is why you find yourself surrounded by Bobs! I would recommend two things: Firstly, you either start to become a better team-player, or become an independent developer. Stay at home, work from your garage, choose solitude! Secondly, if you do encounter an under-performer at work, don't ignore it, don't bitch about it on forums. Do something about it! If, after you have tried to help, they just can't cut it, politely inform your manager. They might have personal issues that you are unaware of, or, they might not like their job, or ... all sorts of things might be affecting their performance. Who knows, one day you might be the 'Bob'. Regards, Colin E.
I agree with this...