[frankish]

Yeah, I think there's a neglect to address that these fixations and best practices are meant to address collaboration and maintenance in a code base. Just cranking out a solution without regard to how others will have to maintain your code does not work so well on a team IMHO.

[wolco]

Are we focusing on making the next teammate's job easier and not focusing on delivering a solution quicker?

[merlincorey]

In an ideal world, I would prefer most every bit of code was written with your fifth replacement in mind.

This means that you've taken the time to document what you've done, test what you've done, and even included any relevant design and architecture concerns for why you have done it.

Without this information, your fifth replacement is likely to have many frustrating "why did they do that this way?" reactions which sometimes will lead to rediscovery of exactly why when they try to remove or change it and are confronted with the context.