I have been in this business for a long time and one thing that is certain is the amount of change we go through. Each day one of our partners, or technology providers will introduce a new way of doing x,y and z and for the most part of the process I have gone along with the ride. Microsoft has been very guilty of shifting gears on technologies and many times even cornerstone technologies such as Data Access.
I have been to many conferences where I could hear the grumblings of developers crying about another thing they would have to learn, or how they just built something on a stack that has been made obsolete
Just recently we hear of the ‘death’ of Silverlight, a RIA technology and one that I quite like. We are also hearing the day to day tribal chants on how HTML5 is going to take over the world. Honestly I cannot personally see how HTML5 is going to have the massive impact and I still can see how the browser manufactures can fragment their implementations to that they are still somewhat incompatible.
But this post was not supposed to be a rant on the frequency of change, or that change happens but the joys of embracing the change. Most of my day now is spent on our consulting services and I do not get as much practical time just playing with technologies. I do read a lot so I know what is going on, and fortunately I am still quite skilled (if I say so myself) at getting in quickly and being to apply new technologies with little resistance.
I decided to get back into the play time with technologies that aligned themselves to what we do here at BITtelligent, so I have jumped into MVC3 with Razor, Code First Entity Framework, and more and more Silverlight. I have to say I have been excited with the outcome of late, especially with the productivity curve.
I really got excited with EF for several reasons
1. It was really quick to get up and running and coding the repository objects using Linq was a win over my old world SQL methods
2. It fits will with some basic integration needs in the SalesLogix space.
With SLX there are several people that have worked on Linq providers that can work against SData or the Database directly but for quick and running requirements that you do not want to carry the platform tax for EF Code First seems like the ticket.
So being said I am not a fan of the box, no sir I do not like it and I will be trying to keep out of one from now on and spending more time with learning, trying and applying the new stuff.