Skip to main content
The Workplace

Return to Question

Tweeted twitter.com/StackWorkplace/status/1283280155432169480
Notice removed Comments only by CommunityBot
Post Unlocked by CommunityBot
deleted 6 characters in body
Source Link
atk
atk
  • 2.4k
  • 1
  • 21
  • 21

I'm a software developer on a team of them. We haveMy team has a variety of development processes that code is technically supposed to go through to get to the master branch.Things Things like unit testing and code review.

The problem is underUnder the slightest amount of pressure from any authority figure (product owner, intermediate developer, scrum master, a desire to finish something before standup/sprint planning, even a random salesperson who claims something is "urgent") they will skip that and force push their fix to master to get it out into production. Our boss agrees that we shouldn't be doing this but he doesn't want to have to fight with people constantly so he just lets it slide and tells me to tell the other developers to push back. 80% of code is now going out without following the process.

The other developers view of the situation is that they will probably be here for another year at most so letting the code rot is cheaper than daily arguments about process with various people who don't value careful engineering.

What can I do about this?

I'm a software developer on a team of them. We have a variety of development processes that code is technically supposed to go through to get to the master branch.Things like unit testing and code review.

The problem is under the slightest amount of pressure from any authority figure (product owner, intermediate developer, scrum master, a desire to finish something before standup/sprint planning, even a random salesperson who claims something is "urgent") they will skip that and force push their fix to master to get it out into production. Our boss agrees that we shouldn't be doing this but he doesn't want to have to fight with people constantly so he just lets it slide and tells me to tell the other developers to push back. 80% of code is now going out without

The other developers view of the situation is that they will probably be here for another year at most so letting the code rot is cheaper than daily arguments about process with various people who don't value careful engineering.

What can I do about this?

I'm a software developer. My team has a variety of development processes that code is technically supposed to go through to get to the master branch. Things like unit testing and code review.

Under the slightest amount of pressure from any authority figure (product owner, intermediate developer, scrum master, a desire to finish something before standup/sprint planning, even a random salesperson who claims something is "urgent") they will skip that and force push their fix to master to get it out into production. Our boss agrees that we shouldn't be doing this but he doesn't want to have to fight with people constantly so he just lets it slide and tells me to tell the other developers to push back. 80% of code is now going out without following the process.

The other developers view of the situation is that they will probably be here for another year at most so letting the code rot is cheaper than daily arguments about process with various people who don't value careful engineering.

What can I do about this?

Post Locked by Neo
Notice added Comments only by Neo
Notice removed Comments only by CommunityBot
Post Unlocked by CommunityBot
Post Locked by Neo
Notice added Comments only by Neo
Mod Moved Comments To Chat
Question Protected by Neo
added 3 characters in body
Source Link
Glorfindel
Glorfindel
  • 3k
  • 5
  • 27
  • 36

ImI'm a software developer on a team of them. We have a variety of development processes that code is technically supposed to go through to get to the master branch.Things like unit testing and code review.

The problem is under the slightest amount of pressure from any authority figure (product owner, intermediate developer, scrum master, a desire to finish something before standup/sprint planning, even a random salesperson who claims something is "urgent") they will skip that and force push their fix to master to get it out into production. Our boss agrees that we shouldn't be doing this but he doesntdoesn't want to have to fight with people constantly so he just lets it slide and tells me to tell the other developers to push back. 80% of code is now going out without

The other developers view of the situation is that they will probably be here for another year at most so letting the code rot is cheaper than daily arguments about process with various people who dontdon't value careful engineering.

What can I do about this?

Im a software developer on a team of them. We have a variety of development processes that code is technically supposed to go through to get to the master branch.Things like unit testing and code review.

The problem is under the slightest amount of pressure from any authority figure (product owner, intermediate developer, scrum master, a desire to finish something before standup/sprint planning, even a random salesperson who claims something is "urgent") they will skip that and force push their fix to master to get it out into production. Our boss agrees that we shouldn't be doing this but he doesnt want to have to fight with people constantly so he just lets it slide and tells me to tell the other developers to push back. 80% of code is now going out without

The other developers view of the situation is that they will probably be here for another year at most so letting the code rot is cheaper than daily arguments about process with various people who dont value careful engineering.

What can I do about this?

I'm a software developer on a team of them. We have a variety of development processes that code is technically supposed to go through to get to the master branch.Things like unit testing and code review.

The problem is under the slightest amount of pressure from any authority figure (product owner, intermediate developer, scrum master, a desire to finish something before standup/sprint planning, even a random salesperson who claims something is "urgent") they will skip that and force push their fix to master to get it out into production. Our boss agrees that we shouldn't be doing this but he doesn't want to have to fight with people constantly so he just lets it slide and tells me to tell the other developers to push back. 80% of code is now going out without

The other developers view of the situation is that they will probably be here for another year at most so letting the code rot is cheaper than daily arguments about process with various people who don't value careful engineering.

What can I do about this?

Became Hot Network Question
Source Link
Eric Yan
Eric Yan
  • 637
  • 1
  • 5
  • 4

How to deal with half my colleagues overriding development processes under the slightest pressure?

Im a software developer on a team of them. We have a variety of development processes that code is technically supposed to go through to get to the master branch.Things like unit testing and code review.

The problem is under the slightest amount of pressure from any authority figure (product owner, intermediate developer, scrum master, a desire to finish something before standup/sprint planning, even a random salesperson who claims something is "urgent") they will skip that and force push their fix to master to get it out into production. Our boss agrees that we shouldn't be doing this but he doesnt want to have to fight with people constantly so he just lets it slide and tells me to tell the other developers to push back. 80% of code is now going out without

The other developers view of the situation is that they will probably be here for another year at most so letting the code rot is cheaper than daily arguments about process with various people who dont value careful engineering.

What can I do about this?