Same old warning against becoming an "architecture astronaut". Look, I understand you got burned and you want to share. However, I'm getting a teeny little bit tired of people who -- out of good intentions -- make it sound like architecture (and clean code and whatnot) isn't important at all.

There's a reason you should pay attention to the state of your codebase. Or rather, there should be a reason for it, one that is better than the intellectual equivalent of wanking. If you're trying to make your code "beautiful" just because you've heard that it's good to keep it "clean" and to "follow every coding standard you've ever heard of", then you're wasting your time.

However, if you're refactoring your code because you found yourself doing the same thing for the 10th time (with small differences), then it's time well spent. If you're spending a bit of effort to structure your code in a way that will help you avoid shooting yourself in the foot (because you've been there and done that and it's no fun at all), then it's effort well spent. And guess what? That's what architecture is all about.

Your users don’t care about architecture, they only care if your app works.

Architecture is what keeps your app working over time.