I don’t want to upgrade beyond SharePoint 2010, at least not right now. I’ve seen 2013, and it’s got some pretty cool features. It also lacks some things that made it easy to customize. I know that 2013 was built so that we the developers couldn’t play around with things that Microsoft feels you shouldn’t have access to unless you have a Little Orphan Annie SharePoint decoder ring or something. And I’m still a bit resentful about that. 2010 is a good solution, and provides a scalable customizable platform upon which you can do a great many things. There are lots of free solutions that extend it further, and virtually limitless aftermarket bolt-ons if you want to go that route. It’s not that I don’t want to learn about the new version, I just don’t think the new version is good enough (yet) to make the jump. I suppose that eventually I will have to. Probably right after I upgrade my home PC from Windows XP.
I love cars. I like to work on them, watch shows about them, and occasionally buy and sell them. I dream of one day owning a classic car that I restore with my son. I can imagine Saturday mornings with him leaning over the fender and pointing out different parts of a motor and how to fix what is broken. One day I envision him and I running a speed shop where we take classic cars like 57 Chevys and Porsche 911s, and restore and modify them to go faster. Most of the time though I find myself fixing my broke down (non-classic) car in my disorganized garage. Where are the vintage automotive signs on the walls and the pegboard neatly organizing my tools? I don’t have a nice clean workbench to do precision work, just a random box to lay tools and parts on. While I fancy myself one day an owner and restorer of classic cars, it seems a far cry from the shadetree mechanic I am today. Working with SharePoint often seems like that to me. I dream of one day building the perfect app or plug-in to “supercharge” SharePoint, but most days I end up fiddling with what is broken or finding workarounds to what doesn’t quite work.