Desmond File

Blog archive

Apple's Ailing Transition

For months, Apple and its CEO Steve Jobs have parried growing rumors about Jobs' declining health. Jobs' alarming weight loss was ascribed most recently to a "hormonal imbalance" that Jobs himself said could be simply rectified without impacting his day-to-day duties at the company.

But now we hear Steve Jobs is sick. Sick enough to take a six-month leave of absence from Apple.

That Jobs is ill should come as no surprise. After all, he survived a harrowing bout with a rare form of pancreatic cancer in 2004. And despite the initial denials and subsequent descriptions of his malady, it was clear to anyone with a good set of eyes that something was seriously wrong with Jobs' health.

Then came the announcement that Jobs would not make a keynote address at the Macworld Expo -- the first time he has failed to appear at the conference since returning to Apple in 1997. And now we get news that Jobs is leaving the company for six months. By comparison, his earlier bout with pancreatic cancer, which required surgery, shelved the energetic CEO for about a month.

As a student of the Cold War (I was a Soviet studies major, of all things, in college), the slow-motion play of events and revelations in this drama sadly mirrors the shaky leadership successions of the old Soviet Union. Kremlinologists were left to scan May Day parade photos and parse the mentions of key Politburo figures in each day's Pravda newspaper to glean hints of where the country might go to next. Facts were impossible to come by, but trends couldn't be hidden. A missed presentation here, a sudden vacation there, and soon evidence mounted that the current leadership might be in real crisis.

Yesterday, we were finally given stark confirmation of what a lot of us feared all along: That Steve Jobs is, in fact, seriously ill and that his leadership of one of the most vital companies in the computing and consumer electronics space is in peril.

By all accounts, interim CEO Tim Cook is a perfect candidate to fill in during Jobs' absence. Well-liked and pragmatic, according to reports, Cook already served once as interim CEO, guiding Apple during Jobs' 2004 absence. But the questions about Apple's future will quickly mount, should it become clear that Jobs will not be returning soon to the company he founded.

For good or ill, the past couple of years have produced a pair of epic leadership transitions in our industry. At Microsoft, we saw a years-long process that was transparent, incremental and controlled. Now at Apple we're witness to an entirely different type of transition -- one shrouded in secrecy and forced by events.

What are your thoughts on how Apple has handled the issue of Steve Jobs' illness? What should Apple do to ensure that it retains the confidence of third-party developers and customers going forward? E-mail me at [email protected].

Posted by Michael Desmond on 01/15/2009


comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube