Yes, the author seems to ignore that there is a difference between good code and bad code. There is an enormous amount of subjectivity in that difference, but s

Yes, the author seems to ignore that there is a difference between good code and bad code. There is an enormous amount of subjectivity in that difference, but sometimes things _are just worse_. Maybe they're worse for the product (e.g. buggy code) or maybe they're worse for the developers (e.g. your tedious build system and global state). Either way, it takes time to do something about.