I love ice cream in nearly any flavor or variety. I’m familiar with it and I enjoy it no matter what the new spin or twist is. You probably feel the same way, except you might not enjoy specific flavors, and that’s ok too.
That’s sort of how I feel about SharePoint customizations when I work on different versions; it’s a cool experience and it’s usually a little different depending on what the flavor of the day is. Sometimes, I’m working on a small UI change and other times I’m building a sophisticated set of features that touch many facets within a SharePoint farm.
When an ice cream maker creates a variety, he or she had specific goals in mind. That person imagines what the customer wants and how they will enjoy it. SharePoint is the same way. The many engineers and quality assurance professionals that toiled on the latest and greatest version of SharePoint had specific goals in mind; some for end-user experience, some for administrators, some for power users, and some for developers. Yes, you, the ever important developer, definitely were in mind as they developed the latest release. You have a great deal of influence on how future versions function.
What’s the point of comparing ice cream and SharePoint? Well, for one, I hope it makes you hungry. I know that I want some right now.
In all seriousness, every release of SharePoint comes with some level of functionality removal, functionality deprecation, and wholly new technologies to leverage. It’s important to try new things in SharePoint, keep current on what the best practices are (because they do change from version to version) and to keep your tools at the ready whether it’s Visual Studio, SharePoint Designer, or a spoon.
I, for one, find that SharePoint 2013 is far more client-side focused that previous versions. I’m pretty certain that I will be writing much more script than server-side code this year. That’s just fine with me. I’ll have my spoon at the ready.