I don't like reinventing the wheel, and I believe that far more experienced people than me have faced problems over and over, and they come with solutions to those repetitive problems, another bunch of experienced engenders faced the same problems and came up with the same solutions, in the end everyone agreed that those solutions are the optimal solutions, and they have started calling them "PATTERNS" , "design patterns" and "architectural patterns". Those patterns will work for you most of the time , in other times you have to alter them to work for you, and in other cases you may have to come with a solution that fits your own use case, or solve your particular problem, but does that make it a pattern? Mostly no...
I don't like reinventing the wheel, and I believe that far more experienced people than me have faced problems over and over, and they come with solutions to those repetitive problems, another bunch of experienced engenders faced the same problems and came up with the same solutions, in the end everyone agreed that those solutions are the optimal solutions, and they have started calling them "PATTERNS" , "design patterns" and "architectural patterns".
Those patterns will work for you most of the time , in other times you have to alter them to work for you, and in other cases you may have to come with a solution that fits your own use case, or solve your particular problem, but does that make it a pattern? Mostly no...
My favorite software architecrure is MSMD. It is the most light weight, nimble and time proven pattern. Prove me wrong.
MSMD? What does MSMD stand for as a software arch? I couldn't find it
@@nyloakamas1337 monkey see monkey do
Lol same
OMG i have googled it man stop 🤣🤣🤣🤣