| Architecture is supposed to be things that help you get the stuff done that needs to get done. Don't confuse architecture with how many repos you have or how big your files are. If you do, you'll end up just moving deck chairs around on the Titanic. Don't confuse architecture with using more logical blocks than you need to. Some people really like making a PizzaFactoryFactory when really they just need to call a constructor. Let architecture be the patterns that help you do the next thing. If something works how it is, you don't need to refactor it. Especially if it's worked like that for a long time. Leave good enough alone. Remember there's a reason why you did things the way you have done them. That's worth a lot more than having a "clean" architecture (which honestly means nothing. clean to one person is a mess to another). If you're going to add features, do it, and make the new architecture choices there. You don't need to change the architecture of everything just because you want to add something. If you did, I'd say that's "bad" architecture. Also, don't let the new tech hype fuel your desire to change everything according to the new hype. If you do new hype you'll not only have to change everything, but you'll end up with bugs from whatever the new hype is anyway. And you'll end up with the same product doing the same things anyway. |