Bullying Support Group
Bullying is the act of intentionally causing harm to others, through verbal harassment, physical assault, or other more subtle methods of coercion such as manipulation. Bullying can be defined in many different ways, but one thing is clear: no one deserves to be bullied. If you or someone you know is coping with bullying, this is the place to share your feelings and get...
Hi,
Looking for advice. Give you some history below. Up to you if you read it or not. My colleague is a constant problem. Due to his limited ability and insecurities. Take a look below. Does this look like a guy that is technically able to you? I'd say 'Hell No' but I'll let you decide.
The guy claims to be really good. Is always self promoting him self and his ability on a daily basis. Poops on everyone else. Resorts to undermining & belittling others especially me, takes credit for other peoples work, constantly poop stirring & trying to score brownie points with MD's....Etc...
The company that have taken over will be looking possibly to make further redundancies.
The only person that is direct threat to this guys job security is me. My job is pretty much identical to his. Aside from a couple of 'basic' supervisory tasks that he has
Colin: is part time/semi retired - not a threat
Lawrence: different job - not a threat
Martin: totally different job - not a threat
Me: Our jobs are almost identical - High threat
For someone that claims to be really good....
Take a look at the bullet points.
1.He has great difficulty in writing small drabs of basic SW regularly. With the semantics, layout and format. I have seen this regularly. He takes credit for other peoples written SW. He lies about what he has done. He said he had created a program for a product. Changes his statement then says he created a module for a test program. Turns out this module has existed for over 15-20 years and he has merely edited it. A line here a word or number there etc... He'll change one word/number in SW or delete one line and claim he has made extensive & complex changes to the SW.
2. When it comes to using test equipment he does not know how to use most of. When forced to use test equipment he passes the task onto another person because of his lack of ability. I have seen this regularly.
3.Gets his science & electronics theory wrong pretty much most of the time.
4.Uses guess work due to lack of technical ability regularly. Almost every time I have seen him work. Example: Working on *** he just randomly swaps equipment around for 2/3 of a day. Every time I have seen him work this is his methodology.
5.Lying -everything he says contradicts everything else he has said. He says I'm not to good at electronics SW is my real skill. Then changes his statement after and claims to be an expert at everything. Curious refer to No.1. ''I've mainly used Lab View''. he says. Well lab view is not proper SW programming it is an icon based system. Were you expand icons and get a table where you put parameters you require in the sections. He did some layout drawing for ***. A pile of paper 2inch thick. He claimed he had done lots of works etc... One day I had to review his paper work and I found that the paper work was padded out with identical multiple copies of the same thing. If one was to remove those copies you'd be left with maybe 5-6 sheets of paper...etc.
6.He has trouble measuring basic potential voltages +/- etc...
7.Lack of technical knowledge. Basic circuitry & theory is held with high controversy and complexity.
8. Lying about almost everything. Example Network analyser S-parameters used at many companies. One moment he says he knows very little about it. ~12Hrs or so later suddenly he says he knows it in depth and always has. He claims he has been the supervisor the company for over six years. Curious cross referenced information from other people. He has only been a supervisor for just around 2 years.
9.Relays are basic devices. I got a 20 min lecture on how a relay works and how complex and controversial they are purely because he believes that there complex.
10.Tells regular self super hero stories of things he has done. What he actually says is both a combination of lies & half truths. ''I wrote a program for ***''. Turns out someone else wrote it and he merely edited to numbers and deleted one line. He does this regularly.
11.Taking credit for other peoples work. Guys from the new company were all standing around Stewart desk while he sat there wowing them by showing work created by another person & taking credit for his predecessors work. I couldn't believe it.
12.Sabotage of equipment to try get leverage over me.
13.Blowing situations out of context & proportion.
14.Skill set that is based solely on familiarity with systems having worked there for 12 years +. 6-8 years spent at the company working in production. Why would an capable engineer work in production? they would not.
15.He took out two files on the entire history of what he has done at the company to try and prove to me that he is technically able. And started telling me a combination of half truths & lies about what he had done. Evidence that actually contradicts most of what he said.
16.Gloating about having a HND. 2/3 of the people at the company have HND's. What a prick.
Oh and there's lots more as you can imagine. I'm sure that's quite enough waffle.
Cheers dave
Looking for advice. Give you some history below. Up to you if you read it or not. My colleague is a constant problem. Due to his limited ability and insecurities. Take a look below. Does this look like a guy that is technically able to you? I'd say 'Hell No' but I'll let you decide.
The guy claims to be really good. Is always self promoting him self and his ability on a daily basis. Poops on everyone else. Resorts to undermining & belittling others especially me, takes credit for other peoples work, constantly poop stirring & trying to score brownie points with MD's....Etc...
The company that have taken over will be looking possibly to make further redundancies.
The only person that is direct threat to this guys job security is me. My job is pretty much identical to his. Aside from a couple of 'basic' supervisory tasks that he has
Colin: is part time/semi retired - not a threat
Lawrence: different job - not a threat
Martin: totally different job - not a threat
Me: Our jobs are almost identical - High threat
For someone that claims to be really good....
Take a look at the bullet points.
1.He has great difficulty in writing small drabs of basic SW regularly. With the semantics, layout and format. I have seen this regularly. He takes credit for other peoples written SW. He lies about what he has done. He said he had created a program for a product. Changes his statement then says he created a module for a test program. Turns out this module has existed for over 15-20 years and he has merely edited it. A line here a word or number there etc... He'll change one word/number in SW or delete one line and claim he has made extensive & complex changes to the SW.
2. When it comes to using test equipment he does not know how to use most of. When forced to use test equipment he passes the task onto another person because of his lack of ability. I have seen this regularly.
3.Gets his science & electronics theory wrong pretty much most of the time.
4.Uses guess work due to lack of technical ability regularly. Almost every time I have seen him work. Example: Working on *** he just randomly swaps equipment around for 2/3 of a day. Every time I have seen him work this is his methodology.
5.Lying -everything he says contradicts everything else he has said. He says I'm not to good at electronics SW is my real skill. Then changes his statement after and claims to be an expert at everything. Curious refer to No.1. ''I've mainly used Lab View''. he says. Well lab view is not proper SW programming it is an icon based system. Were you expand icons and get a table where you put parameters you require in the sections. He did some layout drawing for ***. A pile of paper 2inch thick. He claimed he had done lots of works etc... One day I had to review his paper work and I found that the paper work was padded out with identical multiple copies of the same thing. If one was to remove those copies you'd be left with maybe 5-6 sheets of paper...etc.
6.He has trouble measuring basic potential voltages +/- etc...
7.Lack of technical knowledge. Basic circuitry & theory is held with high controversy and complexity.
8. Lying about almost everything. Example Network analyser S-parameters used at many companies. One moment he says he knows very little about it. ~12Hrs or so later suddenly he says he knows it in depth and always has. He claims he has been the supervisor the company for over six years. Curious cross referenced information from other people. He has only been a supervisor for just around 2 years.
9.Relays are basic devices. I got a 20 min lecture on how a relay works and how complex and controversial they are purely because he believes that there complex.
10.Tells regular self super hero stories of things he has done. What he actually says is both a combination of lies & half truths. ''I wrote a program for ***''. Turns out someone else wrote it and he merely edited to numbers and deleted one line. He does this regularly.
11.Taking credit for other peoples work. Guys from the new company were all standing around Stewart desk while he sat there wowing them by showing work created by another person & taking credit for his predecessors work. I couldn't believe it.
12.Sabotage of equipment to try get leverage over me.
13.Blowing situations out of context & proportion.
14.Skill set that is based solely on familiarity with systems having worked there for 12 years +. 6-8 years spent at the company working in production. Why would an capable engineer work in production? they would not.
15.He took out two files on the entire history of what he has done at the company to try and prove to me that he is technically able. And started telling me a combination of half truths & lies about what he had done. Evidence that actually contradicts most of what he said.
16.Gloating about having a HND. 2/3 of the people at the company have HND's. What a prick.
Oh and there's lots more as you can imagine. I'm sure that's quite enough waffle.
Cheers dave
In general I'd be wary about saying anything unless he does something that directly undermines you or the company and you can effectively document it. I'd say best thing would be to just focus on your job and performance although you can certainly continue to note and document his seedy and dishonest behavior. If you do intend to bring it up to your supervisor or to HR I would just make sure you have documented everything well and you ensure any such discussions are confidential.