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!

Two Critical Questions for Your Next Interview

I’ve interviewed probably over 500 engineering and management candidates over the last several years.  There have been a lot of really smart people who have applied at DocuSign, Microsoft and Tempo Automation. A surprising number of them didn’t have a clear answer to these two essential questions:

Why are you interested in joining our team?Why should we be interested in you? 
If you are an applicant, having a prepared answer for these questions is critical.  If you are a hiring manager, you should ask them and have a clear answer to these questions at the end of the first interaction with your future team mate.

In a field where work is somewhat predictable and static, those questions are less critical, but in software development perseverance, ingenuity and focus make all the difference. These are the two main questions that will separate a subpar and a superb hire.

When I discuss those two questions with an applicant I try to go below the surface.  Generic answers like “it says you ar…

Chief Collaboration Officer

When you search for the word “collaboration” on the Internet, the top hits are mostly software packages you can buy.  Software can facilitate collaboration, but it doesn’t make people collaborate on its own.

One of the key functions of a technical leader is to bring a team together, help people share ideas, and facilitate team members helping each other.  When a software leader overlooks this key function, you end up with a group of individual contributing engineers instead of a cohesive team.
Before we get into tactics, we should ask “Why is collaboration important for an engineering team?” 
It’s critical to examine your assumptions, so here are my reasons for why a group of engineers working on their own are worse than a team working together: Smart people learn from each other.Getting your plans and designs reviewed by other people allows you to leverage their experience and check your assumptions.Collaboration produces artifacts that stay after collaboration has taken place (such…