[danielvaughn]

The point about other people's code rings true for me. What I've been trying to do is gather a collection of good code I've written over the years - solutions that can work for a variety of problems. They're like my own little npm packages, except I have full access to the source and completely understand them inside and out. I can also completely explain how they work to my team, and how they can make changes to the behavior if need be.

[gryn]

A lot of the time it's not characteristics of the code itself but the business mission it needs to fulfill.

good code can give you a lot of headaches if the external business environment sees qualitative changes while that sloppy code over there is has being going hassle free for the last 6 years because the end-goal and patterns that it needs to fulfill didn't change much during that period.