I think any attempt to distil hard earned experience and domain awareness will eventually devolve into misplaced generalisms.

This isn't to say that the article isn't good. It's well written and the teachings are valuable.

This comment is for the inexperienced dev that arrives at theses posts looking for ideological prescriptions: don't.

Give yourself time. Let yourself fail and learn from your mistakes. Keep reading the masters work like Clean Code, SICP, Working effectively with legacy code, software architecture the hard parts, mythical man month etc... but don't let anyone prescribe to you how to do your job.

Developing is ultimately managing an unmanageable and ever evolving complexity and making it work. Developing is art and experience. Developing requires great peace of mind.