I'm curious why this is at the top of HN? My initial thoughts: 1. Title's use of "architecture" is overly vague, but they do define it somewhat in the intro. I

I'm curious why this is at the top of HN? My initial thoughts: 1. Title's use of "architecture" is overly vague, but they do define it somewhat in the intro. It still doesn't seem to overlap with the main bulk of the HN community. 2. Authors aren't listed up front which is frustrating for anyone that has spent time with enterprise work. 3. It's part of a site called "nocomplexity.com". This is frustrating for anyone who's been around the industry for some time because there is a lot of material (good and bad) on these issues. "Complex architecture" and "complicated architecture" often get used interchangeably when the terms mean different things. Many domains are necessarily more complex than others, but you can make a complicated solution to a less complex domain. It's even noted in the Zen of Python.