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!

Highly Effective Software Teams

A few weeks ago our Board of Directors asked me to present my assessment of the state of software.
 I was hired to organize and grow the software team and the directors wanted to know what kind of a team we needed to build.  I was hoping that I can just reference an article somewhere that would give me the answer, unfortunately I didn’t find anything suitable. During my research I did find some great material that will be helpful if your job is to put together a highly effective software team.
A highly effective software team has the following key characteristics: dependable, committed to shared goals, passionate about technology, respectful and compassionate.  These are not limited to technology industry, it can easily apply to finance, medicine, or sports as well.  Below is the summary and references that I found. Dependable If you are creating a software product, you need to deliver your software to your users.  Your users need to know that you are able to solve their problems on …

There are Only Two Ways to Treat Your Team

There are only two ways to treat your team: take care of them or let them go.  Early in my management career there have been times when someone has been underperforming on the team.  Before I knew better I let my emotions get the best of me: I’d give them the cold shoulder, avoid including them in conversations and look like I was upset with them. Thankfully with some good mentorship I came up with a simple rule: we are helping each other or you are off the team.

One of the biggest mistakes that folks make a lot of times is letting people linger on for too long.  Hiring good engineers is hard and getting new folks up to speed is hard.  You feel like you are going to miss your product delivery plan if you let someone go.

Letting folks linger when you are unhappy with each other creates a toxic environment.  This toxic environment is generally contagious and brings the entire organization down.  Of course you can’t have a constant state of euphoria on your team, but if a productive and…