The humming thread (#121, #146, #170) is no longer humming; it’s DEMOING. OpenAI’s GPT-3 API went into beta last month and my Twitter feed has spent the fortnight full of demos that would have been dismissed as staged a year ago: plain-English descriptions turned into working React components; legal prose translated to plain language; essays continued in the style of their opening paragraph; a fake blog post that hit the top of Hacker News before the author revealed the byline. It’s “just” next-token prediction at 175 billion parameters, and the honest staff-level assessment after two weeks of playing with it: it is simultaneously the most impressive parlor trick I’ve ever used and obviously, OBVIOUSLY, a new kind of infrastructure. It confabulates with total confidence (ask it for citations and it invents plausible ones — the failure mode is FLUENCY, which is worse than being wrong badly). It has no idea what it doesn’t know. And none of that changes the trajectory: #121 logged a paper, #146 logged a benchmark-eater, #170 logged a staged release, and this entry logs the first fortnight I watched non-ML engineers build PRODUCTS on the thread. The extrapolation exercise is now everyone’s homework. ...

The us-east-1 Problem (Jul 2020 – Sep 2021) The incidents of this window share a shape: a small, deep dependency — a thread limit, a quota system, one customer’s config — radiating outward until half the internet notices. Postmortem readers learned to ask a new first question: what does everything else depend on? The incidents that defined the period AWS Kinesis / us-east-1, November 25, 2020 — Adding capacity to Kinesis’s front-end fleet pushed servers past an OS thread limit; the fleet needed a slow full restart, and dependent services (Cognito, CloudWatch — and vendors' status pages) failed with it (aws.amazon.com/message/11201). The postmortem taught thousands of engineers what a cell-based architecture is — by describing its absence. Google, December 14, 2020 — The identity/quota system took down Gmail, YouTube, and Google Cloud auth for ~47 minutes: an automated quota migration reported usage as zero and rationed the auth service to death. Safety systems that can’t distinguish “no usage” from “no data” became a postmortem archetype. Slack, January 4, 2021 — First workday of the year; provisioning couldn’t scale up in AWS fast enough, and Slack’s own dashboards were degraded during the response (slack.engineering). OVHcloud fire, March 2021 — A Strasbourg datacenter burned; some customers learned their “backups” lived in the building that was on fire. Physical DR returned to the conversation. Fastly, June 8, 2021 — A dormant bug shipped in May was triggered by one customer’s valid configuration change, dropping ~85% of Fastly’s network. Global outage in seconds; identified in minutes; largely restored in under an hour (fastly.com). Reuters, gov.uk, and Amazon went dark together — 49 minutes that made “CDN concentration” a mainstream news topic. Akamai Edge DNS, July 2021 — A bug triggered by a configuration update took down banks and airlines for about an hour. Same lesson, different CDN. What the postmortems reveal 1. Control plane vs data plane became the sharpest lens. Google’s quota system, AWS’s front-end metadata fleet, Fastly’s config distribution — in each case the management machinery failed while the underlying capacity was fine. “Static stability” (the data plane keeps working when the control plane is down) became the design goal to cite. ...

WWDC today (virtual, prerecorded, and honestly SHARPER for it — the pandemic’s conference format may outlive the pandemic): Apple announced the Mac is leaving Intel for APPLE SILICON — their own ARM chips, the iPhone’s architecture ascending to the desktop, a two-year transition with Rosetta 2 translation for the legacy world. This is the third architecture migration in Mac history (68k→PowerPC→Intel→ARM) and the archive’s #112 deprecation doctrine applies at maximum scale: they announced it with tooling READY (universal binaries, translation layer, dev transition kits shipping now) — the Adobe-Flash three-year-hospice model, executed by the company that owns the whole stack. My prediction, filed for grading: the performance-per-watt numbers from the iPhone lineage suggest the first ARM Macs won’t be “acceptable substitutes” but flatly FASTER than the Intel ones they replace, which will make this the rare migration users request rather than tolerate. (The #136 sweepstake’s Apple-$2T-by-2022 entry is feeling comfortable.) ...

Two Americas shared a split screen this fortnight, and the archive files both because both are true. Saturday May 30th: Crew Dragon FLEW — Bob and Doug to orbit in a capsule with touchscreens, the Falcon 9 booster landing downrange on schedule like the miracle had become a bus route (#073’s crying kid now watches landings with a checklist), dock, hatch open, nine years of gap closed by a company that iterated through explosions in public. The same week: George Floyd was killed by Minneapolis police, and the country erupted into the largest protest movement in its modern history, ongoing as I write, in every city including ours. ...

The fortnight ahead holds the first attempt to launch AMERICAN ASTRONAUTS from AMERICAN SOIL since the Shuttle retired in 2011 — SpaceX’s Crew Dragon Demo-2, Bob and Doug (the actual names; the universe casts well), scheduled Wednesday from pad 39A itself. Nine years of gap, bridged by the company this archive watched land its first booster through a haze of my own tears (#073). The first attempt scrubbed on weather at T-minus-17 minutes — a scrub with humans aboard being the system WORKING (the #151 file’s inverse: a launch culture that treats schedule pressure as a first-class hazard; “the rocket doesn’t care about your press availability” is the healthiest sentence in aerospace). Next window Saturday. The whole locked-down planet could use the launch, which is precisely the pressure the scrub discipline exists to ignore. ...

The layoff wave arrived — travel and mobility first, as their revenue approaches literal zero: Airbnb cut ~25% this week, Uber ~14%, with more queued behind them. The archive files layoffs under #038’s asymmetric-loyalty lesson, but this fortnight adds a CRAFT observation, because the variance in execution was enormous and instructive. Airbnb’s version — a long, specific, personally-signed letter explaining the reasoning; generous severance; healthcare extensions; an alumni TALENT DIRECTORY the company built and staffed recruiters to, actively placing its own laid-off people — was immediately and correctly held up as the standard. The cynical read (“great PR”) and the sincere read (“great leadership”) converge on the same operational fact: how you execute your worst day is a design decision you make BEFORE the worst day, with runbooks, like everything else this blog believes in (#173’s purchasing postmortem has a sibling: every layoff postmortem is a values postmortem — #169’s runtime-configuration lesson at maximum stakes). I took notes I hope never to use. ...

On Monday the 20th, the price of a barrel of West Texas crude oil settled at NEGATIVE $37.63. Sellers PAID buyers to take oil, because the futures contracts expiring that day require physical delivery, storage at Cushing was functionally full, and a “price” is not a fact about a substance — it’s a fact about a CONTRACT MECHANISM meeting a capacity constraint (#136’s consensus-hallucination file gains its wildest exhibit; #110’s “everything is capacity planning” achieves final form: the global oil market ran out of DISK). Retail traders in oil ETFs learned about contango the way juniors learn about rm -rf (#017). The pandemic keeps administering the economy’s chaos-engineering suite with no feature flags. ...

Zoom went from 10 million daily meeting participants in December to a reported 200 MILLION in March — a 20x scale event under global scrutiny, and the fortnight’s twin storylines are the two halves of every scaling story this archive owns. The capacity half: it mostly HELD, which deserves more awe than it’s getting (#149’s concert infrastructure was rehearsed; this wasn’t). The security half: “zoombombing” entered the language (default-open meetings meeting the public internet — permissive defaults are fine at 10M polite corporate users and catastrophic at 200M including trolls; DEFAULTS ARE POPULATION-DEPENDENT, new Proverbs entry), plus a wave of overdue scrutiny (routing questions, “end-to-end encryption” marketing that wasn’t — #137’s material-words file: E2E is a term of art, not a vibe). Their CEO’s response is the template so far: a 90-day feature freeze, all hands to security, weekly public updates. Incident-mode honesty at company scope. Watching with professional sympathy and a checklist. ...

In one fortnight: the WHO declared a pandemic (the 11th), the Premier League suspended its season (the league manager testing positive — the moment the football world’s gut understood), Tom Hanks announced he had it (the moment the rest understood), the market fell so hard it tripped circuit breakers TWICE more (including the worst single day since 1987), and functionally every school, office, restaurant, and border in the Western world CLOSED. The planet just executed the largest, fastest, least-rehearsed migration in human history: physical → digital, everything, everywhere, big-bang cutover, no rollback plan. This blog has spent seven years filing what happens to systems that cut over like that (#019, #130). Now the system is EVERYTHING, and the honest entry is: nobody knows, the load test is live, and we’re all in the incident channel together. ...

Writing this the night of the day the US stock market fell so fast at the open that the EXCHANGE-LEVEL CIRCUIT BREAKERS fired — a 7% drop in minutes, trading halted for a cooldown, the first such halt since 1997 — as an oil price war (Saudi-Russia, choosing THIS week) collided with the pandemic repricing that #174 said one of the two dashboards was owed. Italy expanded its lockdown NATIONWIDE today. The WHO will likely use the P-word within days. The two-dashboards divergence has resolved the way divergences always resolve (#163’s capacitor: slow charge, dead-short discharge). ...