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.

Comments

Popular posts from this blog

Quality of Code is Quality of Life

About 20 years ago when I started working in technology companies I remember “the best” engineers had similar patterns:
-They worked crazy hours
-They knew the systems no one else knew
-They could react and deliver something faster than anyone else
You could always hear other employees say: “Bob is really smart, no one knows how to get anything done in system X besides him!”

This reinforced optimization around being the only person who knew how to do something in some part of the code.  That in turn reinforced job security and bargaining for those engineers, but also chained them to a particular system.  We had big code bases of C++ or Java code where some “Bob” hacked up features as soon as he possibly could.  “Bob” would have occasional nuclear disasters where he’d sleep in the office or through the weekend and then everyone would thank him for how he “saved the day.”  “Bob” sacrificed his quality of life to get praise when he hacked stuff up quickly and then the second time when n…

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!

Code versus Configuration

At Ethos we are building a distributed mortgage origination system and in mortgage there is a lot of
different user types with processes that vary depending on geography.  One of our ongoing discussions is about how much of the logic resides in code vs. being in a workflow system or configuration.  After researching this topic for a bit, I have arrived at a conclusion that the logic should live outside of code very infrequently, which might come as a surprise to a lot of enterprise software engineers.

Costs of configuration files and workflow engines First thing that I assume is true is that having any logic outside of the code has costs associated with it.  Debugging highly configurable system involves not only getting the appropriate branch from source control, you also need to make sure that the right configuration values or the database.  In most cases this is harder for programmers to deal with.  In many FinTech companies where the production data is not made readily accessible…