Let’s imagine the following scenario. You need to develop an application that will require storing data to a repository. If it’s a big project, a group of architects or technical advisors (from company) will be called that will try to design an architecture for the application and identify the stacks/frameworks that will be used.
Usually a company that starts to use a specific framework will use it in all their projects because that framework is already known by them. For example for all projects that needs to persist data they will go for NHibernate even if Entity Framework could be also a good solution – or a NoSQL solution like MongoDB. Another good example is related to SPA frameworks. If they started to use a specific one, than they will stick on it without looking around.
What can happen in this cases?
Well first of all, if you don’t investigate what frameworks/solution could be used to resolve for a given problem you can end using the wrong solution. For example you can end up with an ORM framework that don’t have support for lazy loading, even if this is an important feature for you. You’ll start to do different hacks to support that features.
The interesting thing is that you will reuses that hacks for other projects also. You end up in a vicious circle that will hide the real problem that you have.
In this moment new frameworks and solution appears like mushrooms. Every year new stacks are available on the marker. When you stop looking around and stick on only one solution you are in a train with only one direction – to disaster. In a few years you will provide deprecated solution, on frameworks that are not supported anymore my community or producer.
What you can do to avoid this problem?
The simplest solution is to look around and know what is happening around you. Even if the new solutions are not the best, they may be interesting from different perspective and in time that solution could be better than the one that you already use.
Every time when you start a new project, don’t use the default setup template that you have in mind. For example .Net 4.5, EF, ASP.NET MVC, WCF, Angular.JS. Other solutions could be better that the default setup. Try to investigate what solutions are on the marker and what is the best for your project.
Don’t be afraid of learning curve. This is something normal and you can only benefit from it. Better solution, thinking outside the box, team with more skills, take our of the conform zone the team.
Conclusion
Never stick on a solution/stack because this is what you already know. This will limit you as a person, team from the skills perspective, company from the quality and innovation perspective and the solution that you provide that might not be the best one.
Comments
Post a Comment