Staff Engineers, Oil Money, and the SR-71 That May Fly Again

A piece titled 'The Staff Engineer's Guide to Inventing Work' addressed a structural challenge familiar to senior engineers: at a certain seniority level, contribution shifts from executing assigned work to identifying what work should exist. The author, Sujith Jay, offered a practical rather than abstract framework — describing how to locate problems worth solving when no one is going to hand over a ticket.

An article from The Conversation on oil price economics — 'When oil prices spike, where does the money go?' — drew 95 points and 82 comments. The answer involves a distribution across royalty holders, national oil companies, service companies, refiners, and retailers that differs substantially depending on whether the field in question is a Texas shale operation, a Gulf state sovereign producer, or a deepwater offshore platform. Discussion centered on distinguishing rent extraction from operational margin.

Aviation Week's report that NASA quietly reached out to former SR-71A staffers — engineers, pilots, and maintainers — to explore a secret restart of the program generated the week's most cinematic item. The SR-71 Blackbird was officially retired in 1999, and institutional knowledge required to operate it has been aging out for more than two decades. The decision to contact retired personnel rather than rely solely on documentation suggests either the documentation is incomplete or aspects of the program remain classified even internally. The 184-comment Hacker News thread covered the J58 engine's unusual thermodynamic characteristics — it reportedly transitions from turbojet to ramjet function above roughly Mach 2.2 — and debated what operational gap a restarted SR-71 would fill given the current availability of reconnaissance satellites and high-altitude UAVs.

The week's 'What If We're Wrong?' discussion targeted the confident community narrative around OpenAI's pricing strategy: that 'near-Astra intelligence at a fifth of the price' signals inference commoditization, and that margin must therefore migrate to the agent layer. Three challenges were posed to that narrative. First, benchmark performance and real-world production performance often diverge, and 'near-Astra intelligence' on a leaderboard may correspond to substantially worse results on domain-specific enterprise tasks — in which case the commodity framing collapses. Second, the Pi.dev 'You Said No MCP' post suggests users are actively resisting the permission scope that makes agents genuinely useful; if the market prefers explicit human-controlled tools, neither inference nor the agent layer captures durable margin, and the value may flow instead to enterprise security companies and integration middleware. Third, international regulatory divergence — particularly between the EU's approach to autonomous agents and the U.S. approach — may fragment the market enough to break the scale economies on which a unified always-on product strategy depends.

On the antitrust dimension, a distinction was drawn between market share — which is not itself illegal under the Sherman Antitrust Act — and specific conduct using monopoly power to exclude competition or extend dominance from one market into another. The relevant precedent is U.S. v. Microsoft, where liability followed not from Windows's approximately ninety percent market share but from specific acts: bundling Internet Explorer and conditioning OEM relationships on Netscape exclusion. Observers watching the AI space through an antitrust lens were advised to focus on product bundling, API access terms, and exclusivity arrangements rather than aggregate user numbers. The signal to watch: whether regulators in the EU or the DOJ request internal documents about how Dots pricing and API terms interact with enterprise deals.