Skip to main content

Microsoft Is a Great/Terrible Enemy

Well - the basic point is true "Microsoft is a juggernaut, a terrible enemy to have.", quoted by Mozilla's Scott Collins.

But not for the reasons noted in the article, I prefer to think about how Guy Kawasaki looked at Microsoft (paraphrased):

Microsoft has the ability to turn on a dime. They missed the first Internet revolution - Gates changed the entire company to be internet-focused in less time than it took to release a new product.

Yes, Microsoft is an elephant - but it's an elephant that can turn faster than most mice and that is Microsoft's competitive advantage.

In truth, people would likely prefer IBM or some larger monolith as an enemy - a company that basically takes time to print out blank pages (intentionally left blank) instead of one who basically says "our goal is to beat the market out of whoever we compete with".

Now that's the "theory" of MS competitiveness - the reality of course gets you dealing with lawyers, license agreements and EULAs (enough people have complained about this that I'm not even going to comment anymore).

Scobleizer: Microsoft Geek Blogger

Comments

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...