Programming and Technology blog

Linq to SQL the latest developer drug to be banned?

Recently I have read on various blogs about the demise of one of the newest technologies to enter the .NET framework Linq to SQL.  Well it’s not its demise but from what others have said it’s more like a “don’t count on it being there and updated in the future” statement.  Scott Allen over at OdeToCode has a pretty good blog article about “The Estrangement of LINQ to SQL” and his thoughts on what is going on and how he feels about it.

This is one of the reasons that as a developer of over 10+ years have never really jumped into bed with the latest and greatest technologies/frameworks/methodologies because you never really know if they will be around or supported in a years time.  This is probably why I and a few other developers that I know tend to follow a POD (Plain ol’ Development) process.  While it might not be as glamorous and the talk around the water cooler it surely gets the job done and you more often than not do not get bitten in the ass by the addiction to these gateway drugs.  

Lately it seems that a growing number of developers are showing signs of ADHD (the persistent pattern of impulsiveness part).  Jumping on the latest and greatest just for the sake of “doing it first”.  There are always two sides to the coin, it does drive interesting ideas and development but at the same time I believe that it is creating a whole generation of code that is not maintainable because of how quickly these drugs are dispensed to us and when the next big fix is just around the corner to become addicted to.


Note: some of this article was inspired by a fellow developer and friend Shaneo and his post Linq to SQL, MSTest, Unity – Are These Gateway Drugs?

Comments are closed