Good architecture minimizes the time for developers to read and maintain code, but to make it real, you need to invest significant time in organizing your code and correspondingly money.
To fix it:
Think of architecture in the beginning
Not violate the patterns of the organization of the code during development.
What factors should I take into account before building a new application?
Potential load
if it's an application from scratch and you don’t have an existing application that you want to rewrite or redesign, it doesn’t mean you should make it without thinking about possible difficulties when real traffic starts to grow. If it's hard to predict and calculate, make a beta version with minimal functionality, expose the app to real users, and adapt the next release based on their feedback.
Team experience
You must take into consideration the team's strengths. Don't bet on hype or only your experience. The team should be able to implement ideas into real life with the path of least resistance. The most important is an adequate estimate of the tasks. So, regardless of team experience, always follow the scrum methodology. The deadline is always within sprints.
Fallback plan
When you have only one plan, you don't have anything. If you have two plans, it means you are minimally protected. If your architecture looks theoretically sound but isn’t justified in actual practice, then your team should be ready to switch to a new solution in the early stage. And switch to the best version of the existing solution If you've gone too far.
Follow me on 🐦 Twitter if you want to see more content.
Top comments (0)