Photo by Danist Soh on Unsplash
Any codebase should have good architecture.
Fallacy 1: Grandiosity is required by all enterprise-sized software projects.
Fallacy 2: SOLID principles and a single architecture pattern are not enough.
Letโs discuss Fallacy 1.
When we look at an enterprise such as Google or Microsoft, things get complicated quickly as there are many moving parts. Limiting one teamโs ability to ship code because of another is ill-advised and could be costly in reputation and potential revenue from the new feature. Hence a lot more independent code might be required in this business section.
Enterprises like retailers and other non-direct software-related entities do not require this load of technical debt, which could very quickly become a burning building if left unchecked.
Letโs discuss Fallacy 2.
The SOLID principles are some of the best code principles known by myself. Easy to understand, demanding enough to keep the language of debate at an Intelligent level. Without alienating some lesser experienced developers from the conversation.