Goodbye, Clean Code
&gt; Firstly, I didn’t talk to the person who wrote it. I rewrote the code and checked it in without their input. Even if it was an improvement (which I don’t believe anymore), this is a terrible way to go about it. A healthy engineering team is constantly building trust. Rewriting your teammate’s code without a discussion is a huge blow to your ability to effectively collaborate on a codebase together.<p>I totally disagree one million percent! If you are on my team and you want to rewrite code I wrote (cause it sux) then do it! Don&#x27;t ask, just DO IT! DO IT NOW! Have a blast, tear it apart, rewrite all my shitty abstractions and see if you can do it better. If the result is better code, then awesome! I learn something and the software gets better. If the result is worse code, then awesome! I&#x27;ll tell you why, you&#x27;ll learn something and your improved understanding will allow you to write better code.<p>I also think that a salaried engineer who thinks that a piece of code he or she (but almost always he) wrote is &quot;his&quot; or &quot;hers&quot; is totally wrong. It&#x27;s the company&#x27;s code. Having a false sense of ownership towards that code will just cause grief for that engineer and friction for his or her team.