A coworker pushing code to my projects over my head [closed]

Clash Royale CLAN TAG#URR8PPP

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;

up vote
3
down vote

favorite

Context: I'm a remote worker. I have a few projects I've been working on for quite a few months; my old PM resigned and now I've been moved to another team with these projects.
One of these projects is currently in a process of deployment of a new version with drastic changes, and another is in the first test deployment.
However, these deployments got stuck for a while due to testers (and PM knows about that).

Recently PM asked another guy (working in the office) to help me with these deployments.

So, I supposed he would help me with poking the testers, as he is in the better position to do that. However, instead of this he came up with some ideas to improve the projects to make the deployment easier (which ideas are already on my to-do list, but not of top priority on this stage), and I answered that I'll check his code tomorrow. Then, he pushed his changes directly to the master branch (without creating a pull request), which changes broke the build. I reckon he didn't know well enough what he was trying to do.

So, his help was not really helpful so far, and now this looks like he is just pushing me around.

Q: is it just my paranoia, or this guy is just reckless and incompetent, or he is really pushing me around - intentionally?

What should I do?

UPD so, he has done this with approval of the PM - and without including me into the chain. What means that he is undermining my credibility, and/or PM is unhappy with something in my work. Have I missed something?

communication

share|improve this question

edited Apr 8 '16 at 10:22

asked Apr 8 '16 at 7:41

XenoMind

7161815

closed as off-topic by Lilienthal♦, gnat, user8365, Dawny33, Chris E Apr 8 '16 at 12:59

This question appears to be off-topic. The users who voted to close gave this specific reason:

• "Real questions have answers. Rather than explaining why your situation is terrible, or why your boss/coworker makes you unhappy, explain what you want to do to make it better. For more information, click here." – Lilienthal, gnat, Community, Dawny33, Chris E

If this question can be reworded to fit the rules in the help center, please edit the question.

• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  "Is it just my paranoia? ... What should I do?" How should we know? We don't know your situation, colleague and management structure nearly as well as you do. Have you tried talking to this person? Have you clarified with your PM who's supposed to be in charge of the projects and deployment cycle now? Did you ask how this new person would be positioned in the hierarchy (i.e. below you, next to you, above you)? These are questions that we can't answer.
  – Lilienthal♦
  Apr 8 '16 at 7:59
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  @XenoMind You seem to want to vent your frustrations instead of resolving the problem. You can't do anything without knowing what your actual position and role in the team is. I've given you advice but can't help you if you refuse to hear it.
  – Lilienthal♦
  Apr 8 '16 at 8:56
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  Why don't you just ask the person instead of asking someone else to help you speculate? If you can't, the problem is your team suffers from a lack of communication.
  – user8365
  Apr 8 '16 at 9:43
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  @XenoMind Can you just pick up the phone and call this developer? Hey, your changes broke the build. Just start from there.
  – Brandin
  Apr 8 '16 at 10:30
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  I accidentally pushed code to master this week. I forgot to check my branch out before making a small change. So maybe he did too. Go talk to him.
  – Tony Ennis
  Apr 8 '16 at 12:17
  

  
  
  
  

 | 
show 14 more comments

up vote
3
down vote

favorite

Context: I'm a remote worker. I have a few projects I've been working on for quite a few months; my old PM resigned and now I've been moved to another team with these projects.
One of these projects is currently in a process of deployment of a new version with drastic changes, and another is in the first test deployment.
However, these deployments got stuck for a while due to testers (and PM knows about that).

Recently PM asked another guy (working in the office) to help me with these deployments.

So, I supposed he would help me with poking the testers, as he is in the better position to do that. However, instead of this he came up with some ideas to improve the projects to make the deployment easier (which ideas are already on my to-do list, but not of top priority on this stage), and I answered that I'll check his code tomorrow. Then, he pushed his changes directly to the master branch (without creating a pull request), which changes broke the build. I reckon he didn't know well enough what he was trying to do.

So, his help was not really helpful so far, and now this looks like he is just pushing me around.

Q: is it just my paranoia, or this guy is just reckless and incompetent, or he is really pushing me around - intentionally?

What should I do?

UPD so, he has done this with approval of the PM - and without including me into the chain. What means that he is undermining my credibility, and/or PM is unhappy with something in my work. Have I missed something?

communication

share|improve this question

edited Apr 8 '16 at 10:22

asked Apr 8 '16 at 7:41

XenoMind

7161815

closed as off-topic by Lilienthal♦, gnat, user8365, Dawny33, Chris E Apr 8 '16 at 12:59

This question appears to be off-topic. The users who voted to close gave this specific reason:

• "Real questions have answers. Rather than explaining why your situation is terrible, or why your boss/coworker makes you unhappy, explain what you want to do to make it better. For more information, click here." – Lilienthal, gnat, Community, Dawny33, Chris E

If this question can be reworded to fit the rules in the help center, please edit the question.

• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  "Is it just my paranoia? ... What should I do?" How should we know? We don't know your situation, colleague and management structure nearly as well as you do. Have you tried talking to this person? Have you clarified with your PM who's supposed to be in charge of the projects and deployment cycle now? Did you ask how this new person would be positioned in the hierarchy (i.e. below you, next to you, above you)? These are questions that we can't answer.
  – Lilienthal♦
  Apr 8 '16 at 7:59
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  @XenoMind You seem to want to vent your frustrations instead of resolving the problem. You can't do anything without knowing what your actual position and role in the team is. I've given you advice but can't help you if you refuse to hear it.
  – Lilienthal♦
  Apr 8 '16 at 8:56
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  Why don't you just ask the person instead of asking someone else to help you speculate? If you can't, the problem is your team suffers from a lack of communication.
  – user8365
  Apr 8 '16 at 9:43
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  @XenoMind Can you just pick up the phone and call this developer? Hey, your changes broke the build. Just start from there.
  – Brandin
  Apr 8 '16 at 10:30
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  I accidentally pushed code to master this week. I forgot to check my branch out before making a small change. So maybe he did too. Go talk to him.
  – Tony Ennis
  Apr 8 '16 at 12:17
  

  
  
  
  

 | 
show 14 more comments

up vote
3
down vote

favorite

up vote
3
down vote

favorite

Context: I'm a remote worker. I have a few projects I've been working on for quite a few months; my old PM resigned and now I've been moved to another team with these projects.
One of these projects is currently in a process of deployment of a new version with drastic changes, and another is in the first test deployment.
However, these deployments got stuck for a while due to testers (and PM knows about that).

Recently PM asked another guy (working in the office) to help me with these deployments.

So, I supposed he would help me with poking the testers, as he is in the better position to do that. However, instead of this he came up with some ideas to improve the projects to make the deployment easier (which ideas are already on my to-do list, but not of top priority on this stage), and I answered that I'll check his code tomorrow. Then, he pushed his changes directly to the master branch (without creating a pull request), which changes broke the build. I reckon he didn't know well enough what he was trying to do.

So, his help was not really helpful so far, and now this looks like he is just pushing me around.

Q: is it just my paranoia, or this guy is just reckless and incompetent, or he is really pushing me around - intentionally?

What should I do?

UPD so, he has done this with approval of the PM - and without including me into the chain. What means that he is undermining my credibility, and/or PM is unhappy with something in my work. Have I missed something?

communication

share|improve this question

edited Apr 8 '16 at 10:22

asked Apr 8 '16 at 7:41

XenoMind

7161815

Context: I'm a remote worker. I have a few projects I've been working on for quite a few months; my old PM resigned and now I've been moved to another team with these projects.
One of these projects is currently in a process of deployment of a new version with drastic changes, and another is in the first test deployment.
However, these deployments got stuck for a while due to testers (and PM knows about that).

Recently PM asked another guy (working in the office) to help me with these deployments.

So, I supposed he would help me with poking the testers, as he is in the better position to do that. However, instead of this he came up with some ideas to improve the projects to make the deployment easier (which ideas are already on my to-do list, but not of top priority on this stage), and I answered that I'll check his code tomorrow. Then, he pushed his changes directly to the master branch (without creating a pull request), which changes broke the build. I reckon he didn't know well enough what he was trying to do.

So, his help was not really helpful so far, and now this looks like he is just pushing me around.

Q: is it just my paranoia, or this guy is just reckless and incompetent, or he is really pushing me around - intentionally?

What should I do?

UPD so, he has done this with approval of the PM - and without including me into the chain. What means that he is undermining my credibility, and/or PM is unhappy with something in my work. Have I missed something?

communication

share|improve this question

edited Apr 8 '16 at 10:22

asked Apr 8 '16 at 7:41

XenoMind

7161815

share|improve this question

share|improve this question

edited Apr 8 '16 at 10:22

edited Apr 8 '16 at 10:22

edited Apr 8 '16 at 10:22

asked Apr 8 '16 at 7:41

XenoMind

7161815

asked Apr 8 '16 at 7:41

XenoMind

7161815

asked Apr 8 '16 at 7:41

XenoMind

7161815

7161815

closed as off-topic by Lilienthal♦, gnat, user8365, Dawny33, Chris E Apr 8 '16 at 12:59

This question appears to be off-topic. The users who voted to close gave this specific reason:

• "Real questions have answers. Rather than explaining why your situation is terrible, or why your boss/coworker makes you unhappy, explain what you want to do to make it better. For more information, click here." – Lilienthal, gnat, Community, Dawny33, Chris E

If this question can be reworded to fit the rules in the help center, please edit the question.

closed as off-topic by Lilienthal♦, gnat, user8365, Dawny33, Chris E Apr 8 '16 at 12:59

This question appears to be off-topic. The users who voted to close gave this specific reason:

• "Real questions have answers. Rather than explaining why your situation is terrible, or why your boss/coworker makes you unhappy, explain what you want to do to make it better. For more information, click here." – Lilienthal, gnat, Community, Dawny33, Chris E

If this question can be reworded to fit the rules in the help center, please edit the question.

• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  "Is it just my paranoia? ... What should I do?" How should we know? We don't know your situation, colleague and management structure nearly as well as you do. Have you tried talking to this person? Have you clarified with your PM who's supposed to be in charge of the projects and deployment cycle now? Did you ask how this new person would be positioned in the hierarchy (i.e. below you, next to you, above you)? These are questions that we can't answer.
  – Lilienthal♦
  Apr 8 '16 at 7:59
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  @XenoMind You seem to want to vent your frustrations instead of resolving the problem. You can't do anything without knowing what your actual position and role in the team is. I've given you advice but can't help you if you refuse to hear it.
  – Lilienthal♦
  Apr 8 '16 at 8:56
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  Why don't you just ask the person instead of asking someone else to help you speculate? If you can't, the problem is your team suffers from a lack of communication.
  – user8365
  Apr 8 '16 at 9:43
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  @XenoMind Can you just pick up the phone and call this developer? Hey, your changes broke the build. Just start from there.
  – Brandin
  Apr 8 '16 at 10:30
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  I accidentally pushed code to master this week. I forgot to check my branch out before making a small change. So maybe he did too. Go talk to him.
  – Tony Ennis
  Apr 8 '16 at 12:17
  

  
  
  
  

 | 
show 14 more comments

• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  "Is it just my paranoia? ... What should I do?" How should we know? We don't know your situation, colleague and management structure nearly as well as you do. Have you tried talking to this person? Have you clarified with your PM who's supposed to be in charge of the projects and deployment cycle now? Did you ask how this new person would be positioned in the hierarchy (i.e. below you, next to you, above you)? These are questions that we can't answer.
  – Lilienthal♦
  Apr 8 '16 at 7:59
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  @XenoMind You seem to want to vent your frustrations instead of resolving the problem. You can't do anything without knowing what your actual position and role in the team is. I've given you advice but can't help you if you refuse to hear it.
  – Lilienthal♦
  Apr 8 '16 at 8:56
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  Why don't you just ask the person instead of asking someone else to help you speculate? If you can't, the problem is your team suffers from a lack of communication.
  – user8365
  Apr 8 '16 at 9:43
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  @XenoMind Can you just pick up the phone and call this developer? Hey, your changes broke the build. Just start from there.
  – Brandin
  Apr 8 '16 at 10:30
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  I accidentally pushed code to master this week. I forgot to check my branch out before making a small change. So maybe he did too. Go talk to him.
  – Tony Ennis
  Apr 8 '16 at 12:17
  

  
  
  
  

2

2

"Is it just my paranoia? ... What should I do?" How should we know? We don't know your situation, colleague and management structure nearly as well as you do. Have you tried talking to this person? Have you clarified with your PM who's supposed to be in charge of the projects and deployment cycle now? Did you ask how this new person would be positioned in the hierarchy (i.e. below you, next to you, above you)? These are questions that we can't answer.
– Lilienthal♦
Apr 8 '16 at 7:59

"Is it just my paranoia? ... What should I do?" How should we know? We don't know your situation, colleague and management structure nearly as well as you do. Have you tried talking to this person? Have you clarified with your PM who's supposed to be in charge of the projects and deployment cycle now? Did you ask how this new person would be positioned in the hierarchy (i.e. below you, next to you, above you)? These are questions that we can't answer.
– Lilienthal♦
Apr 8 '16 at 7:59

2

2

@XenoMind You seem to want to vent your frustrations instead of resolving the problem. You can't do anything without knowing what your actual position and role in the team is. I've given you advice but can't help you if you refuse to hear it.
– Lilienthal♦
Apr 8 '16 at 8:56

@XenoMind You seem to want to vent your frustrations instead of resolving the problem. You can't do anything without knowing what your actual position and role in the team is. I've given you advice but can't help you if you refuse to hear it.
– Lilienthal♦
Apr 8 '16 at 8:56

4

4

Why don't you just ask the person instead of asking someone else to help you speculate? If you can't, the problem is your team suffers from a lack of communication.
– user8365
Apr 8 '16 at 9:43

Why don't you just ask the person instead of asking someone else to help you speculate? If you can't, the problem is your team suffers from a lack of communication.
– user8365
Apr 8 '16 at 9:43

4

4

@XenoMind Can you just pick up the phone and call this developer? Hey, your changes broke the build. Just start from there.
– Brandin
Apr 8 '16 at 10:30

@XenoMind Can you just pick up the phone and call this developer? Hey, your changes broke the build. Just start from there.
– Brandin
Apr 8 '16 at 10:30

1

1

I accidentally pushed code to master this week. I forgot to check my branch out before making a small change. So maybe he did too. Go talk to him.
– Tony Ennis
Apr 8 '16 at 12:17

I accidentally pushed code to master this week. I forgot to check my branch out before making a small change. So maybe he did too. Go talk to him.
– Tony Ennis
Apr 8 '16 at 12:17

 | 
show 14 more comments

2 Answers
2

active

oldest

votes

up vote
9
down vote

For non-developers: Your software is typically there in three copies: The "master" version which is THE version that must be handled with extreme care because any problems there can damage your company, the "development" version, which must be handled with care because any problems there can cause trouble to other developers, and your own versions where you are free to do whatever you like. Changing the "development" version without a review is totally unacceptable. Changing the "master" version without heavy review and several people signing off on it is even more unacceptable.

You send an email to the person: "It seems that you checked in changes into the master branch without any review. Could you please remove them as soon as possible? "

If nothing happens, an email to the person and their manager: "It seems that you checked in changes into the master branch without any review. It seems that you haven't removed these changes. Could you please explain to me what you are doing? "

share|improve this answer

answered Apr 8 '16 at 8:29

gnasher729

70.7k31131222

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  This strikes at the heart of the problem... It's not WHAT was the coworkers intention when pushing this code but rather WHY was he able to push that code without review in the first place? It sounds to me like there is a process gap in the OPs source control.
  – DanK
  Apr 8 '16 at 12:12
  

  
  
  
  

suggest improvements | 

up vote
4
down vote

is it just my paranoia, or this guy is just reckless and incompetent, or he is really pushing me around - intentionally?

It's always best to assume idiocy if there is the slightest chance of it. At this point nothing good can come out of assuming otherwise. Hopefully he learnt a lesson.

share|improve this answer

answered Apr 8 '16 at 9:23

Kilisi

94.5k50216376

• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  Nice application of Hanlon's Razor: "never attribute to malice that which is adequately explained by stupidity."
  – MealyPotatoes
  Apr 8 '16 at 10:04
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  Was about to post the same advice ... - but you may want to add, that this is a great chance to educate him on the process and to make sure anyone (PM & other dev) is knowing & agreeing on this process and knows the benefits it provides if followed. ;-)
  – s1lv3r
  Apr 8 '16 at 11:22
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  The corollary, of course is that the malicious, understanding that most will assume idiocy can do darn good impressions of idiots to hide their malice.
  – Richard U
  Apr 8 '16 at 12:04
  

  
  
  
  

suggest improvements | 

2 Answers
2

active

oldest

votes

2 Answers
2

active

oldest

votes

active

oldest

votes

active

oldest

votes

up vote
9
down vote

For non-developers: Your software is typically there in three copies: The "master" version which is THE version that must be handled with extreme care because any problems there can damage your company, the "development" version, which must be handled with care because any problems there can cause trouble to other developers, and your own versions where you are free to do whatever you like. Changing the "development" version without a review is totally unacceptable. Changing the "master" version without heavy review and several people signing off on it is even more unacceptable.

You send an email to the person: "It seems that you checked in changes into the master branch without any review. Could you please remove them as soon as possible? "

If nothing happens, an email to the person and their manager: "It seems that you checked in changes into the master branch without any review. It seems that you haven't removed these changes. Could you please explain to me what you are doing? "

share|improve this answer

answered Apr 8 '16 at 8:29

gnasher729

70.7k31131222

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  This strikes at the heart of the problem... It's not WHAT was the coworkers intention when pushing this code but rather WHY was he able to push that code without review in the first place? It sounds to me like there is a process gap in the OPs source control.
  – DanK
  Apr 8 '16 at 12:12
  

  
  
  
  

suggest improvements | 

up vote
9
down vote

For non-developers: Your software is typically there in three copies: The "master" version which is THE version that must be handled with extreme care because any problems there can damage your company, the "development" version, which must be handled with care because any problems there can cause trouble to other developers, and your own versions where you are free to do whatever you like. Changing the "development" version without a review is totally unacceptable. Changing the "master" version without heavy review and several people signing off on it is even more unacceptable.

You send an email to the person: "It seems that you checked in changes into the master branch without any review. Could you please remove them as soon as possible? "

If nothing happens, an email to the person and their manager: "It seems that you checked in changes into the master branch without any review. It seems that you haven't removed these changes. Could you please explain to me what you are doing? "

share|improve this answer

answered Apr 8 '16 at 8:29

gnasher729

70.7k31131222

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  This strikes at the heart of the problem... It's not WHAT was the coworkers intention when pushing this code but rather WHY was he able to push that code without review in the first place? It sounds to me like there is a process gap in the OPs source control.
  – DanK
  Apr 8 '16 at 12:12
  

  
  
  
  

suggest improvements | 

up vote
9
down vote

up vote
9
down vote

For non-developers: Your software is typically there in three copies: The "master" version which is THE version that must be handled with extreme care because any problems there can damage your company, the "development" version, which must be handled with care because any problems there can cause trouble to other developers, and your own versions where you are free to do whatever you like. Changing the "development" version without a review is totally unacceptable. Changing the "master" version without heavy review and several people signing off on it is even more unacceptable.

You send an email to the person: "It seems that you checked in changes into the master branch without any review. Could you please remove them as soon as possible? "

If nothing happens, an email to the person and their manager: "It seems that you checked in changes into the master branch without any review. It seems that you haven't removed these changes. Could you please explain to me what you are doing? "

share|improve this answer

answered Apr 8 '16 at 8:29

gnasher729

70.7k31131222

For non-developers: Your software is typically there in three copies: The "master" version which is THE version that must be handled with extreme care because any problems there can damage your company, the "development" version, which must be handled with care because any problems there can cause trouble to other developers, and your own versions where you are free to do whatever you like. Changing the "development" version without a review is totally unacceptable. Changing the "master" version without heavy review and several people signing off on it is even more unacceptable.

You send an email to the person: "It seems that you checked in changes into the master branch without any review. Could you please remove them as soon as possible? "

If nothing happens, an email to the person and their manager: "It seems that you checked in changes into the master branch without any review. It seems that you haven't removed these changes. Could you please explain to me what you are doing? "

share|improve this answer

answered Apr 8 '16 at 8:29

gnasher729

70.7k31131222

share|improve this answer

share|improve this answer

answered Apr 8 '16 at 8:29

gnasher729

70.7k31131222

answered Apr 8 '16 at 8:29

gnasher729

70.7k31131222

answered Apr 8 '16 at 8:29

gnasher729

70.7k31131222

70.7k31131222

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  This strikes at the heart of the problem... It's not WHAT was the coworkers intention when pushing this code but rather WHY was he able to push that code without review in the first place? It sounds to me like there is a process gap in the OPs source control.
  – DanK
  Apr 8 '16 at 12:12
  

  
  
  
  

suggest improvements | 

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  This strikes at the heart of the problem... It's not WHAT was the coworkers intention when pushing this code but rather WHY was he able to push that code without review in the first place? It sounds to me like there is a process gap in the OPs source control.
  – DanK
  Apr 8 '16 at 12:12
  

  
  
  
  

3

3

This strikes at the heart of the problem... It's not WHAT was the coworkers intention when pushing this code but rather WHY was he able to push that code without review in the first place? It sounds to me like there is a process gap in the OPs source control.
– DanK
Apr 8 '16 at 12:12

This strikes at the heart of the problem... It's not WHAT was the coworkers intention when pushing this code but rather WHY was he able to push that code without review in the first place? It sounds to me like there is a process gap in the OPs source control.
– DanK
Apr 8 '16 at 12:12

suggest improvements | 

up vote
4
down vote

is it just my paranoia, or this guy is just reckless and incompetent, or he is really pushing me around - intentionally?

It's always best to assume idiocy if there is the slightest chance of it. At this point nothing good can come out of assuming otherwise. Hopefully he learnt a lesson.

share|improve this answer

answered Apr 8 '16 at 9:23

Kilisi

94.5k50216376

• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  Nice application of Hanlon's Razor: "never attribute to malice that which is adequately explained by stupidity."
  – MealyPotatoes
  Apr 8 '16 at 10:04
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  Was about to post the same advice ... - but you may want to add, that this is a great chance to educate him on the process and to make sure anyone (PM & other dev) is knowing & agreeing on this process and knows the benefits it provides if followed. ;-)
  – s1lv3r
  Apr 8 '16 at 11:22
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  The corollary, of course is that the malicious, understanding that most will assume idiocy can do darn good impressions of idiots to hide their malice.
  – Richard U
  Apr 8 '16 at 12:04
  

  
  
  
  

suggest improvements | 

up vote
4
down vote

is it just my paranoia, or this guy is just reckless and incompetent, or he is really pushing me around - intentionally?

It's always best to assume idiocy if there is the slightest chance of it. At this point nothing good can come out of assuming otherwise. Hopefully he learnt a lesson.

share|improve this answer

answered Apr 8 '16 at 9:23

Kilisi

94.5k50216376

• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  Nice application of Hanlon's Razor: "never attribute to malice that which is adequately explained by stupidity."
  – MealyPotatoes
  Apr 8 '16 at 10:04
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  Was about to post the same advice ... - but you may want to add, that this is a great chance to educate him on the process and to make sure anyone (PM & other dev) is knowing & agreeing on this process and knows the benefits it provides if followed. ;-)
  – s1lv3r
  Apr 8 '16 at 11:22
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  The corollary, of course is that the malicious, understanding that most will assume idiocy can do darn good impressions of idiots to hide their malice.
  – Richard U
  Apr 8 '16 at 12:04
  

  
  
  
  

suggest improvements | 

up vote
4
down vote

up vote
4
down vote

is it just my paranoia, or this guy is just reckless and incompetent, or he is really pushing me around - intentionally?

It's always best to assume idiocy if there is the slightest chance of it. At this point nothing good can come out of assuming otherwise. Hopefully he learnt a lesson.

share|improve this answer

answered Apr 8 '16 at 9:23

Kilisi

94.5k50216376

is it just my paranoia, or this guy is just reckless and incompetent, or he is really pushing me around - intentionally?

It's always best to assume idiocy if there is the slightest chance of it. At this point nothing good can come out of assuming otherwise. Hopefully he learnt a lesson.

share|improve this answer

answered Apr 8 '16 at 9:23

Kilisi

94.5k50216376

share|improve this answer

share|improve this answer

answered Apr 8 '16 at 9:23

Kilisi

94.5k50216376

answered Apr 8 '16 at 9:23

Kilisi

94.5k50216376

answered Apr 8 '16 at 9:23

Kilisi

94.5k50216376

94.5k50216376

• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  Nice application of Hanlon's Razor: "never attribute to malice that which is adequately explained by stupidity."
  – MealyPotatoes
  Apr 8 '16 at 10:04
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  Was about to post the same advice ... - but you may want to add, that this is a great chance to educate him on the process and to make sure anyone (PM & other dev) is knowing & agreeing on this process and knows the benefits it provides if followed. ;-)
  – s1lv3r
  Apr 8 '16 at 11:22
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  The corollary, of course is that the malicious, understanding that most will assume idiocy can do darn good impressions of idiots to hide their malice.
  – Richard U
  Apr 8 '16 at 12:04
  

  
  
  
  

suggest improvements | 

• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  Nice application of Hanlon's Razor: "never attribute to malice that which is adequately explained by stupidity."
  – MealyPotatoes
  Apr 8 '16 at 10:04
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  Was about to post the same advice ... - but you may want to add, that this is a great chance to educate him on the process and to make sure anyone (PM & other dev) is knowing & agreeing on this process and knows the benefits it provides if followed. ;-)
  – s1lv3r
  Apr 8 '16 at 11:22
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  The corollary, of course is that the malicious, understanding that most will assume idiocy can do darn good impressions of idiots to hide their malice.
  – Richard U
  Apr 8 '16 at 12:04
  

  
  
  
  

4

4

Nice application of Hanlon's Razor: "never attribute to malice that which is adequately explained by stupidity."
– MealyPotatoes
Apr 8 '16 at 10:04

Nice application of Hanlon's Razor: "never attribute to malice that which is adequately explained by stupidity."
– MealyPotatoes
Apr 8 '16 at 10:04

2

2

Was about to post the same advice ... - but you may want to add, that this is a great chance to educate him on the process and to make sure anyone (PM & other dev) is knowing & agreeing on this process and knows the benefits it provides if followed. ;-)
– s1lv3r
Apr 8 '16 at 11:22

Was about to post the same advice ... - but you may want to add, that this is a great chance to educate him on the process and to make sure anyone (PM & other dev) is knowing & agreeing on this process and knows the benefits it provides if followed. ;-)
– s1lv3r
Apr 8 '16 at 11:22

1

1

The corollary, of course is that the malicious, understanding that most will assume idiocy can do darn good impressions of idiots to hide their malice.
– Richard U
Apr 8 '16 at 12:04

The corollary, of course is that the malicious, understanding that most will assume idiocy can do darn good impressions of idiots to hide their malice.
– Richard U
Apr 8 '16 at 12:04

suggest improvements |