Heavy entry. The world grounded the Boeing 737 MAX this week, every airline, every country, the FAA last among major regulators, after Ethiopian Airlines 302 crashed with the same signature as October’s Lion Air 610. 346 people across the two flights. The emerging picture, assembled from reporting and the Lion Air preliminary findings, centers on MCAS: flight-control software that automatically pushes the nose down based on angle-of-attack data, added to make a re-engined 60-year-old airframe handle like its predecessor, so airlines could skip simulator retraining. Per reporting: it took input from a single sensor (no voting, no cross-check), could re-engage repeatedly against pilot trim inputs, and wasn’t described in the flight manual because the certification strategy depended on the differences not counting as differences. ...

Entry 150. The HQ2 file reopened exactly as flagged: Amazon cancelled the New York half of HQ2 on Valentine’s Day, 25,000 promised jobs withdrawn after sustained opposition to the ~$3B incentive package from local officials and organizers who asked, reasonably, why the world’s most valuable retailer needed a subsidy to hire in the largest talent pool on the continent. The postmortem splits cleanly by prior: “activists cost NYC 25k jobs” vs. “corporate site-selection-as-auction finally met a counterparty with leverage.” My file keeps to the mechanism design: the RFP-as-reconnaissance model works until one bidder audits the terms in public, and then the whole auction’s information asymmetry collapses at once. Virginia keeps its half, quietly, which tells you which negotiation style the machine prefers. ...

The most important live event of the fortnight had no venue: Fortnite held an in-game Marshmello concert, ten-plus million concurrent players attending a virtual show, synchronized worldwide, with physics off and dance emotes mandatory. I attended, professionally (the group chat’s framed receipts obligated attendance). It was genuinely astonishing: not a video in a game, but a shared synchronized experience rendered live for a stadium the size of a mid-tier nation. The infrastructure implications alone (geospatial partitioning, now with a single global hot event on purpose) deserve a conference track, and the cultural implication deserves the decade: the kids’ third place isn’t the mall or the server room, it’s the lobby of a battle royale. Every “metaverse” pitch deck for the next five years just got its slide one, and for once the slide is real. ...

Apple shipped the year’s most intimate bug: Group FaceTime calls could be made to transmit audio from the recipient’s phone before they answered. Call someone, add yourself to the group, and their microphone goes live while their screen still says “incoming call.” Discovered, per reporting, by a teenager trying to set up a game chat, whose mother then spent over a week trying to report it through Apple’s channels before it went viral and Apple killed Group FaceTime server-side entirely. Two files updated: the composition file (the bug lived in the interaction of group-call state machines, each state individually sane) and a new one I’m opening on vulnerability intake: if a diligent citizen with a critical remote-eavesdropping bug can’t reach you in a week, your security program has a 404 where its front door should be. We tested our own security@ inbox Thursday. Response time: 4 hours. Relieved. Also: now monitored. ...

Year seven begins with last entry’s fork already resolving: I spent the fortnight writing the platform-team proposal, headcount, charter, the paved-road philosophy promoted from metaphor to org chart. If it lands, I’ll be a senior engineer who spends 60% of the time on systems whose users are other engineers. Internal platforms are products with the most brutally honest customers alive: they sit ten feet away and they will file the feedback in person, at lunch, forever. Terrifying. Correct. More as the org decides. ...

Entry 146. Six years, 146 fortnights, zero gaps. The streak enters its seventh production year with 99.999% author uptime (one entry written on a phone in an Oregon eclipse field; the SLA held). 2018’s thesis: everything got invoiced. 2017 ran up the bills; 2018 collected. Facebook paid for the feed (Cambridge Analytica, $119B in a day, the token heist). Musk paid per word ($4.4M/token). TSB paid for the skipped rehearsal. Fallout 76 paid for shipping the wrong vision competently. Marriott paid for buying a breach sight-unseen. And the whole industry paid its GDPR retrofit costs for a decade of data hoarding, the only invoice that came with a receipt I’m actually proud of (the deletion pipeline; the lawyers’ forcing function produced my year’s best work, therapy pending). ...

Tumblr’s adult-content ban takes effect Monday, announced two weeks ago (proximate cause: a child-safety app-store removal; structural cause: Verizon-owned Tumblr’s ads business needing brand safety), and executed via an ML content classifier whose false positives have become a genre unto themselves: flagged sand dunes, flagged classical sculpture, flagged Tumblr’s own announcement post. Two lessons for the file. One: content moderation at scale is classifier deployment at scale, and shipping a high-stakes model with that precision profile is the ML equivalent of the TSB cutover; the confusion matrix is the product. Two, the bigger one: communities are load-bearing (the Reddit lesson) and this is its corollary: a platform purging its core community’s content is a migration event for that community, and the diaspora (Twitter, bespoke sites, Discord) is already routing around the damage. Platforms are temporary; archives are personal. Export your things. ...

Marriott disclosed today: the Starwood reservation database was breached for four years, since 2014, predating Marriott’s own acquisition of Starwood, exposing up to 500 million guests: passports, travel histories, the occasional unencrypted card. Two archive threads converge with a clang. First, the M&A angle: Marriott bought this breach in 2016 and ran it unknowingly for two years. Due diligence audits the books, the brand, the real estate, and treats the IT estate as furniture; “you acquire their attackers too” belongs in every deal memo (Yahoo’s discount was the precedent; a breach literally repriced that acquisition, and the industry filed it under “Yahoo problems”). Second, the duration: four years of dwell time. Breach detection lag is the metric nobody dashboards; prevention gets the budget, detection gets a log-retention policy written by the finance team. (The ceiling rule applies; expect the passport count to firm upward.) ...

Stan Lee died Monday at 95, and the internet performed the full global grief ritual (the Prince protocol) for the man whose collaborative mythology (with Kirby, with Ditko; the footnotes built half of everything, same week’s lesson) became this century’s shared narrative operating system. The MCU is architecture: twenty films on a common continuity substrate, the boldest long-term integration project in entertainment (the Infinity War snap was its TSB-scale cutover, executed clean). Excelsior, and credit the co-authors. ...

The GitHub outage of October 21st got its postmortem this week, and it’s an instant classic of the genre, the kind I’ll assign to juniors like homework: a routine maintenance event caused a 43-second network partition between GitHub’s East and West coast datacenters. Forty-three seconds. The failover automation, doing exactly its job, promoted a West Coast MySQL primary while the East Coast primary held seconds of writes that had never replicated. Split-brain: two databases, each believing itself the truth. And here’s the decision that makes it teaching material: GitHub chose consistency over uptime, running degraded for 24+ hours to reconcile data rather than serve wrong answers fast. The postmortem says so, explicitly, trade-off by trade-off. That’s the maturity frontier: not preventing all failure (43 seconds of network weather defeated a world-class team) but choosing your failure mode in advance and documenting the choice like an adult (rehearsed audacity, ops edition). Our own failover’s partition behavior is now a scheduled game-day. I checked. Nobody knew the answer. That’s the finding. ...