A team is not a fiefdom. Using "authority" to handle conflicts likely won't lead to good results. Different people need different guidance, and overall manage

A team is not a fiefdom. Using "authority" to handle conflicts likely won't lead to good results. Different people need different guidance, and overall management seems poor at dealing with people. Also: "[implementing] a private variable in a class" is not a "task". A diff should be a single idea (i.e. have a purpose on its own). Adding unused code with no purpose just makes it likely that code will stay dead forever. In codebases I work in, an unused variable would be a lint error and that code could never ship. > If you are iterating and being “agile”, then you can remove it later realizing your mistake, and if you code it right, then it will not be intertwined into code so deep that is causes a delay. It seems like the author hasn't worked with a large code base before. With a constant pressure to ship, dead code can sit around in your repo for a long while--and often good engineering initiatives aren't incentivized as much as they should.