There is a lot of rants in this article (more towards the end). It's great to be self reflective about how you do things, how you think, etc, and what choices y

There is a lot of rants in this article (more towards the end). It's great to be self reflective about how you do things, how you think, etc, and what choices you make and why, but this started to get preachy and state absolutes that other people should follow or take heed of. I've been doing software for 40+ years, and one observation I've made and it's something that keeps happening is people giving very definitive rules and advice, some of these end up becoming peoples guiding principles/values (things that are good, things that are bad) and mostly it just serves to put blinkers (blinders in the US?) on people and slows down exploring other ways of thinking about software. I get why we do this, and I get why someone wants to preach to newcomers (as this article states) and why we want to try and take our experiences and encode them into guiding principles, but it is easy to forget you only have the tiniest of windows on the world of software development. I think it's much more important to tell our stories, explain our reasoning, reflect on how we could do better and what we would do with 20/20 hindsight. Luckily on HN we see a lot of this style of writing.