I&#x27;m all for constructive criticism, and if a process is burning more money than it is generating I&#x27;d speak my mind too. But many of our new fish (at least around here) don&#x27;t like how much of a stickler I can be for proper documentation, good naming conventions, using the bug tracking system etc. They see it as pointless bureaucracy because they don&#x27;t report to our boss, who when he asks &quot;how are things going&quot; likes to hear and see more than me just saying &quot;good.&quot;<p>While there are plenty of processes out there that likely don&#x27;t need to be, there are I&#x27;d venture a lot more where the value generated isn&#x27;t necessarily obvious to the guys in the trenches. I&#x27;m happy to explain this to anyone who asks (and have) and we occasionally even have an issue crop up where hey, look how useful this &quot;busywork&quot; you did earlier is right now, but the point is to a certain degree you should expect to simply obey the stated rules even if you don&#x27;t IMMEDIATELY see their value. It&#x27;s just respectful.<p>I&#x27;d also say it&#x27;s far too easy to conflate &quot;mindless obedience&quot; and &quot;respectful behavior&quot; these days.