To your point about getting software out the door.  I&#x27;ve run into a type of developer on more than one occasion that I call &quot;refactoring kings&quot;.  Invariably, they&#x27;re on the hunt for commits and how they can make it &quot;better&quot;.  Of course any 20 lines of code has the possibility of being refactored infinitely to a better state.<p>That said, the post was pretty spot-on, if a little tongue-n-cheek.  The trick is to know what battles to fight.  I&#x27;ve recently come aboard a small team where the main developer is more of a DBA than &quot;coder&quot;, so there&#x27;s lots of best practices missing.  But we&#x27;re in a startup mode, and I don&#x27;t have the time to refactor the whole damn thing.  If I see something egregious, I&#x27;ll fix it, but there&#x27;s code battles that I&#x27;ll defer for another day.