Skip to main content

Why not to use default solution for any type of project

In today post we will talk about how why is not a good thinks to use a ‘template’ solution/setup for any project.
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

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

[Post-Event] Codecamp Conference Cluj-Napoca - Nov 19, 2016

Last day I was invited to another Codecamp Conference, that took place in Cluj-Napoca. Like other Codecamp Conferences, the event was very big, with more than 1.000 participants and 70 sessions. There were 10 tracks in parallel, so it was pretty hard to decide at  what session you want to join.
It was great to join this conference and I hope that you discovered something new during the conference.
At this event I talked about Azure IoT Hub and how we can use it to connect devices from the field. I had a lot of demos using Raspberry PI 3 and Simplelink SensorTag. Most of the samples were written in C++ and Node.JS and people were impressed that even if we are using Microsoft technologies, we are not limited to C# and .NET. World and Microsoft are changing so fast. Just looking and Azure IoT Hub and new features that were launched and I'm pressed (Jobs, Methods, Device Twin).
On backend my demos covered Stream Analytics, Event Hub, Azure Object Storage and DocumentDB.

Title:
What abo…