I read the article and was pleasantly surprised, although after some consideration it was more like this:
If you haven't already started working with SQL Server 2016 this is definitely the time. Here are some suggestions:
Get in front of this now - we can't all be like this:
Hope this helps!
Monday, May 2, 2016
SQL 2016 - The Time Has Come!
Microsoft dropped it on us this morning: