By John Gruber
WorkOS: APIs to ship SSO, SCIM, FGA, and User Management in minutes. Check out their launch week.
Derek Thompson, writing for The Atlantic:
Six months ago, I wrote that Americans had embraced a backwards view of the coronavirus. Too many people imagined the fight against COVID-19 as a land war to be waged with sudsy hand-to-hand combat against grimy surfaces. Meanwhile, the science suggested we should be focused on an aerial strategy. The virus spreads most efficiently through the air via the spittle spray that we emit when we exhale — especially when we cough, talk loudly, sing, or exercise. I called this conceptual error, and the bonanza of pointless power-scrubbing that it had inspired, “hygiene theater.”
My chief inspiration was an essay in the medical journal The Lancet called “Exaggerated Risk of Transmission of COVID-19 by Fomites.” (Fomites is a medical term for objects and surfaces that can pass along an infectious pathogen.) Its author was Emanuel Goldman, a microbiology professor at Rutgers New Jersey Medical School. At the time, Goldman was a lonely voice in the wilderness. Lysol wipes were flying off the shelves, and it was controversial to suggest that this behavior was anything less than saintly and salutary. Other journals had rejected Goldman’s short essay, and some were still publishing frightening research about the possible danger of our groceries and Amazon packages.
But half a year later, Goldman looks oracular. Since last spring, the CDC has expanded its guidance to clarify that the coronavirus “spreads less commonly through contact with contaminated surfaces.” In the past month, the leading scientific journal Nature published both a long analysis and a sharp editorial reiterating Goldman’s thesis. “A year into the pandemic, the evidence is now clear,” the editorial begins. “Catching the virus from surfaces — although plausible — seems to be rare.”
Adam Lashinsky profiled Tim Cook for Fortune in 2008, and a few months later, when Steve Jobs began an extended medical leave for his liver transplant, I pulled the following quote from Lashinsky’s profile:
One day back then, he convened a meeting with his team, and the discussion turned to a particular problem in Asia. “This is really bad,” Cook told the group. “Someone should be in China driving this.” Thirty minutes into that meeting Cook looked at Sabih Khan, a key operations executive, and abruptly asked, without a trace of emotion, “Why are you still here?”
Khan, who remains one of Cook’s top lieutenants to this day, immediately stood up, drove to San Francisco International Airport, and, without a change of clothes, booked a flight to China with no return date, according to people familiar with the episode. The story is vintage Cook: demanding and unemotional.
“Boring” does not seem the right word.
[Sabih Khan], by the way, is now on Apple’s senior leadership team as SVP of operations — the title Jeff Williams held before becoming COO, and the title Cook himself held when he joined Apple in 1998.
Feature story for Bloomberg Businessweek,* by Austin Carr and Mark Gurman:
Cook came to Apple in 1998 after a dozen years at IBM Corp. and a six-month stint at Compaq and seemed, at least to old Apple hands, devoid of any obvious personality. He’d work 18‑hour days and send emails all through the night. When he wasn’t at the office he seemed to live at the gym. Unlike Jobs, he had no pretensions to being an artist. “Tim was always pure work: grind, grind, grind, grind,” says one former Apple executive who worked with Cook in his early years at the company and who, as with other sources in this story, spoke on the condition of anonymity because of nondisclosure agreements and fear of corporate reprisals. “I always found him exceptionally boring.”
The magazine cover is a play on Cook’s obvious contrasts with Steve Jobs: “Here’s to the sensible ones, the team players, the problem solvers, the round pegs in the round holes…”
Is Cook boring, though? His public persona certainly is staid. He’s very rarely knocked off what feel like prepared talking points in his public remarks. And even when he opens up, he doesn’t reveal much. But is he boring, or just so intensely private and self-controlled that he comes across as a bit of a cipher to those who aren’t close to him?
This Businessweek piece is a good report — very fair, and rings true. There’s not much new in it for close followers of Apple, but it’s a good primer for those who aren’t. It ably addresses what I see as Apple’s and Tim Cook’s biggest risk: the almost indescribable scope of the company’s reliance on China for manufacturing. Here’s a bit:
[Foxconn founder Terry] Gou always seemed happy to accommodate, often building entire factories to handle whatever minimalist-chic design specs Apple threw at Foxconn. Jon Rubinstein, a senior vice president for hardware engineering during Jobs’s second tour at Apple, recalls almost having a heart attack in 2005 when he went with Gou to see a new factory in Shenzhen for the iPod Nano — a tiny device 80% smaller than Apple’s original MP3 player — only to find an empty field. Within months, though, a large structure and production line were in place. “In the U.S. you couldn’t even get the permits approved in that time frame,” he says.
* Bloomberg, of course, is the publication that published “The Big Hack” in October 2018 — a sensational story alleging that data centers of Apple, Amazon, and dozens of other companies were compromised by China’s intelligence services. The story presented no confirmable evidence at all, was vehemently denied by all companies involved, has not been confirmed by a single other publication (despite much effort to do so), and has been largely discredited by one of Bloomberg’s own sources. By all appearances “The Big Hack” was complete bullshit. Yet Bloomberg has issued no correction or retraction, and seemingly hopes we’ll all just forget about it. I say we do not just forget about it. Bloomberg’s institutional credibility is severely damaged, and everything they publish should be treated with skepticism until they retract the story or provide evidence that it was true.