I’m not following SharePoint, no, but you have to be blind not to have noticed there is a new version coming out. Like I said two years ago and started describing three years ago.
Doesn’t matter. What matters is how it’s done.
Let me point out a few of Microsoft’s “here’s what’s coming” projects.
.NET Open Source
During Connect, Microsoft announced they were open-sourcing .NET and porting it to Linux and Mac. Here’s more or less how that happened.
“Hey, we’re open-sourcing .NET. It should be on Github in a few moments. Whoops, there’s the first public pull request, I was hoping to do that myself.”
In other words: here’s what we’re going to do and here it is, as ready as it is, probably full of problems, but we could really use your help in making this better. Thanks a bunch, you’re awesome!
A bit earlier than connect, Microsoft also announced that Windows 9 would never be, but instead would be a brave attempt at unifying all current and some future device platforms into one OS. Here’s more or less how that announcement happened:
“Hey, we’re betting the barn on this new version of Windows. It should be on insiders.windows.com in about 24 hours. It will probably break and frustrate the crap out of you, but we really could use your help in making this better. Thanks a bunch, you’re awesome!”
A bit later, they even made a video to thank those of us that have tried Windows 10:
This is Microsoft’s flagship by far; the most important piece of software, perhaps on the planet. It works great and they’ve made important changes based on the feedback from users.
So, how is the announcement of SharePoint 2016 going? Following the same pattern? Will they look at the launches of the open early access programs for Windows 10 and .NET and learn from it? Will they finally hear what people have been saying for years?
Like earlier versions, there’s possibly something coming at some time later, maybe this year if everything goes according to plan. Want to help Microsoft make it better?
You have to prove to Microsoft that you are worthy to be part of the early access group. I guess that’s slightly different from earlier versions, where only MVPs and a few secrecy-clad clients were allowed to “help out” (although in reality, it was all set in stone before anyone outside of Redmond got a say).
Will You Help?
For SharePoint 2010 and SharePoint 2013, I spent considerable time and resources to disclose information about the upcoming versions. This time, I won’t.
The SharePoint ship is sinking, and although some people claim that is a crystal ball prediction, I don’t want to be part of it.
The massive success of the strategy I have proposed for six years is now proven, on scales the size of which would make the SharePoint team jizz in their collective pants. The massive failure of the app model in SharePoint 2013 could have been avoided had they told the world what lunacy they were planning. It could have saved SharePoint 2013.
Rather than listen, however, the crew of the ship, namely the SharePoint team, will go down with their decision to go against virtually the entire community and even now the evidence from their own company.
Feel free to ask me again why I think it’s a stupid idea to be in SharePoint. There was hope until early 2012. Now, all there is are far too few life rafts and a stubborn group playing violins.
As you may know, I’ve left the SharePoint scene to do things I believe have a brighter future. Search the blog for more details and I’ll leave the ranting for now.
Regardless, the path on which I’m currently walking is mobile app development. I want to see whether it’s fun, which it currently is, and possibly whether I can make a living from it.
I’ve done a number of apps so far, and most of these are what I call grinding apps. It’s a term I started using during the days of USPJ Academy for exercises you use to get the basics of a task or task set into your blood, so to speak. Repeat the basics often enough and they get so familiar you can spend actual time on build great software rather than plumbing.
However, I’d like to start looking at more useful apps and while I’m doing so, I’ll work on an apprentice’s salary. That’s great news for you because that means you can hire a highly experienced and skilled developer at a fraction of the price you’d normally pay.
When doing SharePoint development, I invoiced $200 per hour because I was worth that much (and in virtually all my projects, I delivered way more value than $200 per hour). I still do that for SharePoint, but for mobile app development, you can currently hire me for a mere $50 per hour.
No, I don’t negotiate, but like I’ve always done, I charge only when I’m actually producing value or code for you. If I’m fumbling or have to learn new stuff to do tasks for you, that’s on my time, not yours.
I do Android and Windows Phone development, and I can probably pick up iOS if it’s absolutely vital to you. I can build in Xamarin or native code and I’d be happy to offer advice on which options make sense.
Keep in mind, though, that although you will get production grade code, fully tested and verified, harnessing my over 20 years of professional and 30 years of hobby software development experience, I’m doing this to learn, so the calendar time taken may be longer than you expect.
But here’s the rub… I may even work for free for you. If you have a fun, interesting, or particularly worthy project, or you are an awesome person or work for an awesome organization, as judged solely by me, I may work for free for you. That may be the whole project or parts of it, for example to get to a proof-of-concept stage for funding or something like that.
So, what are you waiting for? Ah, yes, how to reach me.