Skip to main content

Model CEOs- Who do you trust?

Interesting article on the worst CEOs around.

I was surprised by the list but then when you consider the current stock prices, I guess not.

Ellison is no big surprise. The one thing that people who go up against Microsoft really need to consider is that the ones who do it successfully don't make broad claims or try to "beat them legally". They do it with product.

Oracle has a great enterprise database but the tools are terrible (why they can't build a good GUI IDE is beyond me). But what makes it worse is that Ellison makes Scott McNealy (of Sun) look like a boy scout. He's arrogant to the point of being rude whenever he talks about his competition and with what he is trying with PeopleSoft, he's obviously lost his original belief in true capitalistic values.

Let the MARKET decide. Microsoft isn't without fault in a lot of its licensing agreements. Do I trust Microsoft? Maybe the question should be Do I trust Microsoft's lawyers in writing an agreement? Get rid of the lawyers and let the market decide fairly and unequivocally.

In the software arena, the market will decide (look at Quicken vs. Money for an old but meaningful example). I love Money but the latest version (2004) is actually harder to use than the 2000 version. MS doesn't have to rely on agreements (despite what nay-sayers may think) - but I think now they end up simply defending past practices (rightly or wrongly), instead of saying "we're wrong - let's go it on our own". They need to be more like their own development teams and just let the market go for it.

In the same vein, these noted CEOs have tried to buy their way to success instead of relying on their own ability. MS buys companies too but in the case of Oracle - they should realize that when the door is being slammed in their face for the umpteenth time, it's time to go home.

MSN Money - SuperModels

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...