Steve Miller's Blog

A digital workshop for systems-minded tech commentary.

Author: steve

  • Houthi Seizure of Mokha and Red Sea Chokepoints Helps Push U.S. Diesel Past $6

    Houthi Seizure of Mokha and Red Sea Chokepoints Helps Push U.S. Diesel Past $6

    Diesel is the bloodstream of physical logistics. When it hits a record, you do not need a TED Talk to explain why groceries, construction, and warehouse ops get grumpy.

    In mid-September 2026, Iran-backed Houthi forces seized Yemen’s Red Sea port city of Mokha (Mocha), then pressed control over nearby coastal points and islands that sit on the approach to the Bab el-Mandeb Strait—the gate between the Red Sea and the Gulf of Aden. CNBC, The National, and The Guardian described a rapid coastal advance (Mokha, Perim/Mayyun, later Hanish islands in subsequent reporting) that tightens leverage over a shipping lane already stressed by attacks and embargo threats against Saudi-linked traffic.

    How a Yemeni port shows up on an Ohio fuel board

    AAA data reported by NBC News and CNN put the U.S. national diesel average at about $6.05–$6.06 on September 11—first print above $6, above the June 2022 record of $5.82. By September 15, AAA figures cited in market coverage had diesel near $6.27 nationally, with California much higher. Crude benchmarks were hanging around or above $100 as Red Sea and broader Middle East risks stacked.

    Important honesty check: diesel’s spike is multi-causal. Coverage also points to tight distillate inventories, high refinery utilization, Russia-related product disruptions, and the wider Iran-linked conflict’s effect on Gulf shipping—not a single pier in Mokha acting alone. The port seizure is an accelerant and a risk premium, not a magical price formula.

    Sources:

    Tech infrastructure without the cartoon

    Yes, many data centers keep diesel for generators. Treating every generator test as a budget apocalypse is oversell; treating fuel as free forever is worse. The bigger channel for most IT organizations is indirect: trucking costs into hardware supply chains, delayed rack deliveries, higher colo operating fees, and customers whose own freight inflation shows up as slower projects.

    If you want an operator checklist instead of a doom scroll:

    1. Know your generator burn rate and contract terms before the next heat wave coincides with $6 fuel.
    2. Ask vendors about freight surcharges on servers and networking gear; silence is not a discount.
    3. Map dependency on Red Sea / Suez routings for the SKUs you actually order—not a generic “Asia” blob.
    4. Separate crude headlines from distillate balances. Gasoline and diesel can diverge; diesel is the freight fuel.

    Diesel into “everything”

    Economists quoted in national coverage made the unsexy point: diesel is embedded in trucking, agriculture, and construction. When it prints records, CPI categories beyond the fuel gauge start arguing. Pair that with August’s gasoline-driven CPI pop and you get a feedback loop policymakers hate—energy shocks that threaten to stick into core via services and goods handling.

    For tech ops, generator diesel is the vivid anecdote; freight is the P&L. If your hardware lands late, your project plan is fiction. Build schedule slack like you build RAID: assume a disk (or a strait) misbehaves.

    Red Sea vs. Hormuz: two doors, one mood

    Analysts keep reminding markets that Bab el-Mandeb and Hormuz are different doors on the same house. Houthi coastal gains stress the Red Sea door; Gulf conflict stress hits Hormuz. Saudi Petroline was part of the attempt to exit via the Red Sea when the Gulf door jammed. When both stories worsen in the same fortnight, freight and fuel markets stop pretending these are independent tickets.

    Ship-traffic snapshots—such as reported halving of Bab al-Mandeb crossings on a given day—are volatile. Use them as weather reports, not eternal laws. The strategic fact is simpler: more Houthi control nearer the strait raises the option value of harassment and raises insurance and routing costs even when a given tanker still passes.

    Household translation

    $6 diesel is not only truckers’ pain. It is the quiet markup inside contractor quotes, municipal budgets, and the price of anything heavy. If your family budget already felt August gasoline, diesel is the sequel that shows up in everything that arrives by pallet.

    Bottom line

    Houthi control along Yemen’s Red Sea coast raises the probability of disrupted or detoured shipping through Bab el-Mandeb at the same moment U.S. diesel is printing records. That combination taxes every system that moves atoms—including the atoms inside your next server shipment. Plan logistics like you plan redundancy: assume the primary path gets interesting.

    Steve Miller — Mason, Ohio. Former programmer, sysadmin, and IT manager. Still checks the generator dipstick.

  • Treasury’s $6B Long-Bond Buyback Bought Only $5.19B—Yields Still Climbed

    Treasury’s $6B Long-Bond Buyback Bought Only $5.19B—Yields Still Climbed

    When a fix is smaller than the incident queue, the monitoring dashboard does not cheer. Neither did the Treasury market.

    On September 10, 2026, the U.S. Treasury executed an expanded buyback of longer-dated notes—debt in the roughly 10- to 20-year remaining-maturity bucket—after announcing a maximum of $6 billion, up sharply from prior $2 billion operations. Bloomberg and follow-on market reports say Treasury actually purchased about $5.19 billion, declining richer offers rather than filling the full max. Bids exceeded $10 billion; selectivity was the point. The 10-year yield pushed toward 4.95%, levels not seen since 2023 in several write-ups; the long end also sold off, with some desks citing multi-year highs on the 30-year.

    This was not a failed auction in the classic sense

    Buybacks are optional purchases with price discipline. Treasury’s rules allow buying less than the stated maximum when offers are unattractive. Calling it a “failure” in the stub’s sense is tabloid shorthand. The market lesson is blunter: a few billion against a tens-of-trillions debt stock will not reprice the term premium by itself, especially while inflation stickiness and deficit math keep investors demanding more yield.

    Reuters’ take matched what bond people muttered in plain English: tripling the buyback size sounded supportive; it did not console investors worried about long-end supply and government financing needs. The New York Times similarly described an underwhelmed market reaction when the $6 billion plan was first detailed.

    Sources:

    Why infrastructure readers should care

    You do not need a fixed-income desk seat to feel higher long yields. They feed mortgage rates, project finance, municipal borrowing, and corporate capex discount rates. Hyperscale campuses, utility interconnects, and AI data-center builds are duration-sensitive bets. When the risk-free curve jumps, “we’ll cheaply finance the next hall” becomes a spreadsheet argument, not a slogan.

    Think of the buyback as a liquidity micro-patch. Useful for specific off-the-run issues and market functioning. Not a substitute for fiscal path credibility or inflation control. If your leadership team heard “Treasury is buying bonds, rates will fall” and greenlit a levered expansion, revisit the model.

    Operator takeaways

    1. Re-price WACC on multi-year builds; do not wait for the next print to surprise the board.
    2. Separate liquidity support from yield ceilings. Buybacks can help plumbing and still coexist with rising yields.
    3. Watch the long end if your contracts reference 10-year-linked financing or power-hedge tenors.
    4. Avoid narrative overfit. One $5.19B operation is a data point, not a regime change.

    A note on “Bessent’s buyback”

    Secondary coverage frames the expanded operation as part of Treasury Secretary Scott Bessent’s effort to support long-end liquidity and influence borrowing costs. Whether you like the politics or not, the market scored the play on size and price discipline. In systems terms: you announced a bigger patch window, then declined noisy commits that failed code review. Developers understand that. Bond traders do too. What neither group believed is that a $6 billion ceiling would rewrite a structural yield story overnight.

    Comparing patches: buybacks vs. rate policy

    Do not confuse Treasury buybacks with Federal Reserve policy. One is a debt-management and liquidity tool. The other sets the overnight policy rate. They can point different directions in the same month—especially with stubborn CPI and political pressure swirling around the Fed. Your treasury and CFO partners should keep those wires straight when they explain “why financing moved” to a product team that just wants more racks.

    For municipal and school-district IT readers: higher long yields ripple into bond issuances that fund fiber, HVAC, and secure networks. The $810 million gap between $6B max and $5.19B bought is tiny in federal terms and still educational—optionality cuts both ways when the buyer has standards.

    Incident language for finance

    If this were a Sev-2, the timeline would read: announced larger mitigation → executed with price guardrails → metrics (yields) still red → declare partial mitigation, continue watch. Nobody competent would call the guardrails a bug. Nobody competent would call the red metrics a success either.

    Bottom line

    Treasury showed up, bought less than the headline maximum on purpose, and the bond market kept demanding a fatter premium to hold long duration. That is price discovery, not a sitcom about a group-project spreadsheet. For anyone funding real infrastructure, the signal is simple: capital got dearer, and a small buyback did not talk it back down.

    Steve Miller — Mason, Ohio. Former programmer, sysadmin, and IT manager. Still reads the fine print on “up to” limits.

  • AI Extinction Warnings Hit Washington—While Kill-Switch Bills Race Memes

    AI Extinction Warnings Hit Washington—While Kill-Switch Bills Race Memes

    Two conversations run on the same Wi-Fi and barely wave at each other. One is people generating cat memes and slide decks with chatbots. The other is researchers saying, in public, that loss-of-control scenarios for future systems are not a rounding error.

    In early September 2026, Anthropic alignment lead Evan Hubinger wrote that he earnestly believes AI could kill all humans and personally puts the chance above 10% within a decade, while arguing the industry lacks a solved plan for aligning superintelligence. Coverage in The Guardian, The Independent, and Anadolu’s factbox roundup placed those remarks alongside other lab and ex-lab warnings—and a burst of lawmaker statements demanding hearings, standards, shutdown authorities, or pauses.

    Separate “today’s model” from “tomorrow’s feedback loop”

    Hubinger and careful explainers emphasize a distinction the stub blurred: concern concentrates on future systems that can accelerate their own development, not on your helpdesk bot drafting an email. That nuance matters. Flattening it produces either panic or eye-rolling, both of which are useless for change control.

    Meanwhile, Congress and outside advocates have floated overlapping tools with very different teeth: bipartisan “kill switch” concepts that would require shutdown capabilities for frontier systems; “Stop Rogue AI”-style authorities for agencies to identify and halt dangerous systems on their networks; and more maximalist calls—from some progressives—for bans or moratoria on artificial superintelligence or new data centers. Reuters noted a widening set of lawmakers reacting after Anthropic-linked warnings circulated.

    Sources:

    Bureaucracy meets production reality

    Here is the sysadmin translation. Extinction risk is a tail-risk management debate. Most outages you will personally debug this year are prompt injection, poisoned agents, data leakage, GPU cluster power draw, and sloppy access keys. Those are not “distractions from extinction.” They are the secure-development habits that either exist or do not when stakes get higher.

    Compliance theater is real: fifty-page assessments while hobby projects share the same cluster. The fix is not more poetry about kill switches. It is staged rollouts, eval gates, auditable logs, contained tool use, and the organizational courage to delay a launch when evals fail—without waiting for a senator’s press conference.

    What I’d want in any serious bill

    1. Clear capability thresholds so rules hit frontier training runs, not every startup chatbot.
    2. Mandatory eval + incident reporting with whistleblower teeth.
    3. Shutdown and access-control requirements that are tested, not slideware.
    4. Honesty about energy and security externalities without pretending a data-center pause is a complete alignment strategy.

    Memes are not the opposite of safety

    People will keep using models for jokes while labs argue about tails. That coexistence is not hypocrisy; it is how general-purpose tools work. The policy failure is when meme familiarity becomes an excuse to skip evals, or when extinction rhetoric becomes an excuse to ignore present-tense harms—bias in benefits systems, scams, cyber uplift, energy siting fights. Hold both stacks in your head. It is uncomfortable. So is on-call.

    International echo chamber

    The Guardian also flagged UK political attention—peers and MPs wrestling with superintelligence risk language from figures like Stuart Russell and others. Treat multinational treaty talk as early-stage: letters and briefings are not ratification. Still, when labs, legislators, and foreign parliaments synchronize vocabulary around catastrophic risk, corporate risk registers that only list “chatbot brand safety” look thin.

    If you advise a CIO, translate the week into three buckets: (1) present cyber/scam/agent risks you can mitigate now; (2) energy and siting fights tied to cluster growth; (3) governance commitments you may be asked about if you train or host frontier-adjacent systems. Bucket 3 is where extinction rhetoric becomes a board question even if your company only fine-tunes.

    Humor, dry, as promised

    The funny part is not extinction. The funny part is watching the same company blog promote consumer agents while its researchers post career-limiting probabilities on social media. That tension is information. Markets price products; governance has to price tails. If your risk committee laughs the tails away because the demo sings, you have restated every industrial accident report’s first chapter.

    Bottom line

    Researchers are stating extinction probabilities out loud; lawmakers are drafting shutdown metaphors into statutes; users are still asking models for recipes. The gap is funny until you notice it is also a governance gap. Treat frontier scaling like a high-impact change window: evidence, rollback, and someone on-call who can say no.

    Steve Miller — Mason, Ohio. Former programmer, sysadmin, and IT manager. Keeps a kill switch for bad deploys—and still wants the runbook written down.

  • August 2026 Was the Hottest August on Record—Grids and Cooling Feel It First

    August 2026 Was the Hottest August on Record—Grids and Cooling Feel It First

    You do not need a satellite to know August was mean. The agencies brought receipts anyway.

    NOAA’s National Centers for Environmental Information said August 2026 was the warmest August in its 1850–2026 record: 1.32°C (2.38°F) above the 20th-century average, beating the previous tied 2023/2024 marks by 0.08°C. June–August was also record warm globally. Global ocean temperatures set a new August high; El Niño helped torch parts of the tropical Pacific. Copernicus/ECMWF ERA5 put August’s global surface air temperature at 16.96°C, the warmest August in that dataset and jointly the warmest calendar month alongside July 2023, about 1.65°C above its pre-industrial baseline estimate.

    Different baselines, same story: the thermometer stack is not debating whether August was exceptional.

    Sources:

    Daily life without the melting-BBQ bit as the whole story

    Yes, outdoor plans get ugly when heat indexes go ridiculous. The infrastructure story is larger:

    • Peak power. Residential AC and commercial cooling synchronize. Utilities sweat reserve margins.
    • Data centers. Inlet temperatures and cooling plant efficiency worsen; water use and power use climb together for many designs.
    • Workers and logistics. Warehouses, last-mile delivery, and outdoor maintenance shift hours or slow down—quiet GDP friction.
    • Compounding hazards. NOAA noted above-average global tropical cyclone counts in August even as the Atlantic stayed odd under El Niño; regional heat and fire risk remain the local face of a global mean.

    The stub’s “heat credits for off-peak data processing” line sounded like a product press release that does not exist as a standard SKU. Demand-response programs for homes and some commercial loads are real. Treat vendor marketing as marketing.

    What operators should actually do

    1. Revisit design-day assumptions for cooling. Last decade’s PUE brag may assume weather that is now optimistic.
    2. Test generator and UPS behavior under simultaneous heat + grid stress, not only in spring tabletop drills.
    3. Coordinate with utilities early on large load additions; interconnect queues do not care about your model launch date.
    4. Separate climate attribution debates from facilities engineering. You can argue policy and still raise the chilled-water set of problems that pay the bills.

    Mason summers and facility truth

    Southwest Ohio humidity turns “hot” into “your cooling coils are working overtime.” Homes feel it as bills. Facilities feel it as approach temperatures and condenser performance. If your runbook still assumes 2010 design days, August 2026 is your page-one postmortem input. I will keep grilling occasionally. I will also keep telling boards that climate averages are capacity inputs, not culture-war props.

    El Niño is not a free pass for operators

    NOAA tied part of the Pacific heat to ongoing El Niño. That helps explain maps; it does not excuse weak facilities planning. El Niño years rearrange who gets the worst of rain, drought, and cyclones. Your campus still needs cooling headroom and a grid-outage plan for the heat dome that shows up on a Tuesday.

    Copernicus noting a return above 1.5°C versus pre-industrial for the month is a policy alarm bell and an engineering yellow flag. Boards that only discuss ESG adjectives should add a slide with condenser approach temperatures and water risk. Boring slides prevent exciting outages.

    One more practical note for homeowners reading along: demand-response and pre-cooling with a smart thermostat are real tools. They will not cancel a record global month. They might keep your transformer happier between 4 and 7 p.m. That is enough virtue for one paragraph.

    Wildfire and flood footnotes

    Record heat rarely travels alone. Even when your metro is not on fire, supply chains that feed cooling equipment, transformers, and replacement fans cross regions that are. Build vendor geographic diversity into spare strategy the way you diversify cloud regions—imperfect, still better than a single factory town.

    North America logging its warmest August in NOAA’s regional notes is the part local readers should not skip. Global means hide uneven pain. If your region set records while oceans set records, your utility’s peak-day planning packet needs a refresh before next summer’s first heat advisory.

    Bottom line

    August 2026 set August records in major global datasets and tied the warmest month mark in Copernicus’s accounting. That is not a lifestyle blog cue; it is a capacity-planning input for grids, cooling plants, and anyone whose uptime depends on physics. Grill if you must. Size your heat rejection for the world you are getting.

    Steve Miller — Mason, Ohio. Former programmer, sysadmin, and IT manager. Still respects the second law of thermodynamics more than summer optimism.