Skip to main content

Why Office for iPad makes sense in the world of Satya+Larry+Tim

Microsoft is a new company.  I think just about everyone who doubted that is now absolutely clear that MSFT under Steve Ballmer is nothing like the company under Satya.  Number one thing is clear is that
Satya understands the new landscape.  The new landscape right now is this:
1) the number one personal computing device company is Apple
2) the number one consumer cloud company is Google

Both of these companies are looking to get into the lucrative business of being the number one business productivity company because that's a multi billion dollar business and a huge platform with tentacles throughout the world that matters.

It looks like Satya decided not to waste his time fighting the current forces head on.  That strategy has been employed by Steve Ballmer who was still hoping that Microsoft can outgun the competition like it's 1999.

Satya comes from cloud services background which he turned from zero to a formidable competitor to Amazon Web Services.  He completely understands that in the new multi-device world it's more critical than ever to be the keeper of user's data and the enabler of business productivity.

Microsoft now brings the productivity and data to you "where you are" instead of limiting to the devices that run Windows.  The battle ground is no longer who controls the OS API.  The battle ground now is who controls your data.  Just like 20 years ago it was important to provide the solutions and infrastructure to access your disk, graphics card and get input from your mouse, today it's important to be able to share information, verify identity, and provide security that transcends corporate firewalls.

This is the place where Microsoft has a fighting chance to be the top dog.  They can give consumers what they want - responsive and beautiful software that takes advantage of device capabilities, ubiquitous data formats and cloud services.  On the developer front they can give developers what they want: excellent IDE which works well with the Cloud (read Azure), reliable identity services across all devices and API for cloud based data.

Microsoft will still keep their "horses in the race" with Windows Phone and Surface and continue working with hardware manufacturers, but I think we will see more and more of the Microsoft Cloud services offered to all the devices and all the developers.  This in turn is going to change the company from a software licensing to a cloud computing revenue model.

I am really looking forward to BUILD conference this week.  My guess is that there will be more options for cross platform developments where all roads lead to the Microsoft Cloud.
Post a Comment

Popular posts from this blog

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!


SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!

Hire Fast, Fire Fast? Not so Fast.

Silicon Valley is full of advice and it frequently comes from people who have little experience on the subject matter.  A popular topic surrounds hiring and terminations with the king catch phrase being: “Hire Fast, Fire Fast.”  To me, what that usually means is lack of diligence, thought, communication and courage.

When hiring people love going with their gut feel, often with disastrous results.  There is an obvious subject of diversity of thought, appearance and background.  When thinking “fast” you are probably hiring people like yourself because humans quickly react to people who they believe are in their tribe.

A startup that lacks the resources of a big company often becomes so desperate to get technical staff that when a decent candidate comes along, excitement ensues and the employer doesn't slow down to put them through a more rigorous hiring process.

I highly encourage technical founders and engineering executives to write out their precise hiring process.  Of course, y…

Pull Requests and Code Reviews

Software development involves a great deal of collaboration.  One of the most basic blocks of collaboration on a software development team is a code review.  There have been many different ways of doing code reviews over time, some of this has been dictated by the tools available.  Git and online source collaboration tools created a set of best practices that are worthwhile of adopting on any team.

About a month ago I have looked at various articles about how to best create a Pull Request (PR) and do a code review and the attached presentation is the result of this research.  The presentation can help you guide your team and develop a set of collaboration practices that works for your particular situation.

It’s good to start out with why to seek a code review.  Having clarity about your intentions helps you guide the person helping you with code reviews and also to manage your expectations about you can get out of the code review.  The reasons for seeking a code review are generally …