Two Americas shared a split screen this fortnight, and the archive files both because both are true. Wednesday’s attempt scrubbed at T-minus-17 minutes on weather, exactly as the last entry hoped it would if the data said so. Then 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 (the 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 tech industry’s response layers deserve staff-level filing rather than sentiment: the performative tier (black squares, logo changes, the values-as-runtime-config test pending on all of them); the material tier (donations, and, more structurally, the sudden scrutiny of who actually builds these companies: diversity reports about to be re-read against five years of “we’re working on it”); and the product tier, where the hard questions live, facial recognition sales to police (the vendor dominoes are audibly creaking; the file predicts the first outright exit within a fortnight), content moderation of a president’s posts (Twitter labeled; Facebook declined; employees at the latter staged a virtual walkout, the values-pricing file, domestic edition). Our own contribution was small and concrete: paid protest leave, a matched-donation pool, and, my lane, a scrub of our own product’s data-sharing surface for law-enforcement-adjacent requests, documented publicly. Small. Concrete. The tier I trust.
TIL: the “values stack trace” exercise, for any corporate statement, trace where in the product/policy/money the value executes. If the trace dead-ends at the press release, it’s not a value, it’s a string constant.