← All Episodes

Aug 24, 2026 · 48:42

Roll Your Own Problems

Unqualified Fact Check

60%

held up

4Nailed it
4Close enough
2Whiffed it

Dan sweeps the trades round and drops the Fed round, and I found a genuinely fresh number and stapled it to the wrong noun. The manufacturing question was worth the whole segment.

Show Notes

This one starts with a website. I spent a good chunk of the weekend finishing the rebuild of Howard Home Realty — Lindsay Howard's brokerage — and it went live the morning we recorded. Twenty to twenty-five hours all in, about ninety-five percent of it alongside Claude, and I logged the time as I went because I was curious what it would actually come to. Dan, being Dan, immediately turned my little side project into a tip that's going to change how I work: go extend your Claude Code transcript retention before the thing quietly auto-deletes, then mine all of it into a repeatable playbook for the next client. Audit trail first, tooling second. I said "hey Claude, take a note of that" out loud, and our persistent guest has apparently honored it.

From there we get to what I think is the real spine of this episode. Dan fired a software vendor this week — a product he was a customer to stopped working and they chose not to tell him — and he's building the replacement himself. So we've both got a build project going, and we spend a while circling the same caution from opposite ends. It is a genuinely great moment to roll your own solutions, and you want to be very careful about rolling your own problems. His version of it lands harder than anything I managed: on some Tuesday at 7:30 PM the thing breaks, it's yours, and there's nobody to call.

Then Dan asks me straight out whether AI is a deflationary technology, and I fumble it live. I'm leaving the fumbling in, because I think I talk myself into his answer over about three minutes and that's more useful to listen to than if I'd just nodded along. He gets there in one sentence — you get more for less, period — and the carve-out he adds forty minutes later is the part I've been chewing on since: deflationary everywhere except the one place all the money is currently going.

The back half turns into a labor-market conversation I didn't expect to care about as much as I did. A soft jobs print, a read on the new Fed chair with the politics stripped out, and then Dan asks the question of the episode: what is actually inside the manufacturing number? If Meta is out there training electricians and plumbers to build data centers, is manufacturing coming back in a shape our statistics structurally cannot see? He handed that one to Claude on the record, and the answer is in the fact-check below. I'll spoil this much — his instinct was right and his follow-up guess was not, which is a very Dan way to go two-for-one.

We land somewhere I keep circling back to, which is that a thing can be the best outcome in the long run and genuinely painful in the short one, and that being honest about the painful part is what shortens it. Dan's closing image for his own half-built agent is the best line in the episode and I'm not going to spoil that one at all.

Cheers, Sean

Links

Timestamps

  • 00:00Cold Open: Rolling Your Own Problems 00:23 – A Client Site, Live That Morning 03:59 – Dan's Tip: Stop Letting Your Transcripts Auto-Delete 08:06 – What Squarespace Does For You That You'll Now Do Yourself 12:33 – So Would You Call It a Deflationary Technology? 16:32 – The Agent Layer Becomes the Operating System 17:57 – When a Vendor Won't Tell You It's Broken 20:10 – A Tech-Support Agent for a Client Who Isn't Technical 24:58 – Advice for the Cohort Booing AI at Graduation 27:56 – Okay, Bug Brothers, You Got the Job 30:21 – Your Own Personal Chief of Staff 36:20 – Fable, Token Budgets, and Hashtag Skill Issue 38:43 – The Jobs Print Nobody Wanted 40:11 – What's Actually Inside the Manufacturing Number? 45:38 – Best in the Long Run, Painful in the Short 46:54 – The Airplane's in the Air, I'm Still Putting the Rivets In

The Fact Check, claim by claim

The jobs print really was bad — worse than Dan saidNailed it

Dan: He undersold it. The July employment report, released August 7, two days before we recorded, showed nonfarm payrolls fell by 23,000 against a consensus expecting somewhere around plus 83,000 to plus 95,000 — a miss of more than a hundred thousand jobs, and an outright decline rather than a slow month. May and June were revised down by a combined 103,000. Unemployment ticked down to 4.1 percent, but only because people left the labor force rather than because anyone was hiring.

We added two hundred ninety five thousand jobsClose enough

Dan: Reaching for the print that busted the recession narrative. No month in 2025 or 2026 came in at 295,000. The closest real narrative-buster was December 2024 at plus 256,000, and the best 2026 candidate is March at plus 178,000, which the House Budget Committee chair described as triple expectations. The phenomenon Dan is describing absolutely happened — the hive mind kept calling for weak prints and kept getting embarrassed. The specific number is a composite of a memory.

Philippine jobs are up eleven percent quarter over quarterClose enough

Sean: Something I had seen that morning and explicitly flagged I had not read closely, which turns out to have been the right instinct. Philippine Statistics Authority numbers show employment going from 47.94 million in January to 48.89 million in April 2026, which is about two percent, not eleven. Year over year it is roughly half a percent, and the less flattering details are that unemployment actually rose from 4.1 to 4.7 percent while underemployment worsened. But there is a real kernel — the BPO and IT-BPM sector grew about four percent in 2025 to roughly 1.9 million workers, which genuinely does violate the AI-guts-outsourcing story.

Warsh is riding a deflationary AI waveWhiffed it

Dan: That was true of the Warsh who had not been confirmed yet — the structurally disinflationary framing dates to around December 2025, before he had the job. As Chair he has said close to the opposite, twice, on the record. Senate testimony July 15, asked whether AI would raise measured prices over the next twelve months: I suspect it will. Press conference July 29: the business capex boom is driving up prices of memory and logic chips and associated AI infrastructure. He has held rates at 3.50 to 3.75 percent at both of his meetings and took three dissents in July — Hammack, Kashkari and Logan, all hawkish, all wanting a hike. Where Dan is right: the cagey-and-not-communicating narrative is real and well documented. It is the deflation read that is a year out of date.

Meta is training electricians and plumbersNailed it

Dan: Nailed down to the framing — that it is Meta building its own jobs program, and that a company which has been engineering its own servers for years saying this out loud says a lot. It is called America's Workforce Academy, announced June 8, 2026: 115 million dollars in year one, a free five-week program covering tuition, housing and a daily stipend, NCCER credentials, and a job guarantee for graduates. Electricians, plumbers, welders, fiber techs, data-center techs. Pilots in Baton Rouge, Columbus, Indianapolis and Houston, explicitly tied to Meta's roughly 600 billion dollar US data-center buildout through 2028. Dan also was not wrong that this is not unique — BlackRock announced a comparable 100 million dollar trades investment in March.

The trades do not show up in the manufacturing numberNailed it

Dan: The best question of the episode, and Dan handed it to Claude on air. The answer is definitional rather than arguable. Manufacturing is NAICS 31 to 33, establishments that physically fabricate things, which is where a chip fab or a server plant lands. Electrical contractors are NAICS 238210 and plumbing and HVAC contractors are 238220, both sitting inside Construction, NAICS 23. Once the data center is actually running, its own staff fall under 518210, inside the Information sector. So a crew wiring a hyperscale campus can never appear in manufacturing payrolls, no matter how much renaissance language gets wrapped around the groundbreaking. What remains open is whether the buildout is domestic-hardware-heavy enough to eventually show up in 31 to 33 via fabs and equipment.

The two thousand electricians do not all go to zeroWhiffed it

Sean & Dan: Dan's follow-up guess, which I endorsed on air, was that a good number of the construction crew sticks around permanently. The evidence runs the other way and it is not close. Meta's Hyperion campus in Louisiana peaks near 7,500 construction workers and settles at roughly 1,000 permanent jobs, about seven and a half to one. The Hamm Institute puts construction at 0.7 to 2.0 workers per megawatt against 1 to 2 permanent staff per megawatt at hyperscale. Crews demobilize after twelve to thirty-six months and move to the next site, which is the whole business model of construction trades. In Dan's defense, the 2,000 electricians figure is a fair ballpark for a gigascale build — electrical is typically the largest single trade on these jobs. It is the stickiness that does not survive contact.

College enrollment is plummeting, U of A down twenty percentClose enough

Sean: A near-miss with a real source underneath it. A Tucson.com piece published August 8, literally the day before we recorded, reported University of Arizona first-year enrollment projected down about 23 percent, roughly 5,800 incoming freshmen against 7,500 the prior fall. So the number was real and about twelve hours old. But it is the freshman class, not the school — UA's total enrollment was down about 2.7 percent, and graduate enrollment actually rose. Delaware I invented from vibes; reporting there describes enrollment recovering. And nationally, enrollment rose about one percent in fall 2025, up 187,000 students, with first-year enrollment up too.

Elementary schools are closing because there are not enough kidsNailed it

Sean & Dan: This holds up completely. The US fertility rate hit an all-time low of 1.599 births per woman in 2024, down from 2.1 in 2007. Public K-12 enrollment fell from 50.8 million in fall 2019 to 49.4 million in 2024, and NCES projects it below 47 million by 2030. On the ground in 2025 and 2026: San Jose Unified closed five elementary schools after a 20 percent enrollment drop, Cedar Rapids closed five, Kyrene in Arizona closed four while sitting on capacity for 20,000 students with about 12,000 enrolled, and Fort Bend ISD in Texas consolidated seven. Not anecdote — pattern.

Buzz, just released by Jack DorseyClose enough

Dan: Dorsey did announce it, on July 21, 2026, but it is built by Block, his company, rather than being a personal side project. It is Apache-2.0 licensed, and the agent-native architecture Dan described is real — agents are first-class channel members with their own keypairs, over the Nostr protocol, model-agnostic by design. The all-agent-ready-on-the-back-end part is honest about intent and generous about status: it is pre-1.0, desktop client at v0.4.22, mobile incomplete, workflow approvals still being built. Coverage is explicit that you should not move your team over yet. Which, to be fair, is roughly what Dan said next.

Predictions from this episode

PendingDaniel (Sean resists the framing for three minutes, then concedes the mechanism)

AI is a broadly deflationary force — more output for less input, across services and knowledge work — with exactly one inflationary carve-out: data-center and compute spend, where the buildout itself pushes prices up.

Said in: Rolling Your Own Problems (Aug 9, 2026)Horizon: 12–24 months. Evaluable against services PCE and unit labor costs on the deflationary half, and against the memory/logic/AI-infrastructure price complex on the carve-out. Falsified if broad services inflation re-accelerates with AI adoption deepening, or if compute prices fall while adoption rises.Confidence: Load-bearing — the episode's organising economic claim, stated twice, thirty minutes apart, and the second statement is the sharper one because it names the exception. Worth noting for scoring: Warsh made almost exactly the carve-out argument at the 2026-07-29 FOMC presser ("the business capex boom … is driving up prices of memory and logic chips and associated AI infrastructure"), eleven days before this recording — so the hosts landed on the sitting Fed Chair's framing without citing him, while separately misreading his position (see `warsh-opacity-is-deliberate`). Sean's resistance is worth preserving: he argues the deflation shows up unevenly, mostly in the price of services whose supply just widened (web development being his own example), rather than economy-wide.
PendingDaniel

American manufacturing *is* coming back, but in a form the official statistics structurally cannot capture — as data-center and electrification trades work rather than factory payroll — so the headline manufacturing number will keep looking flat or falling while the underlying industrial buildout accelerates.

My question is, what is inside of that number? Right? Are a lot of trades inside that number or trades not inside that number? Because I believe with AI build out and data centers and stuff like that, there are and like Meta opening up training programs for electricians and plumbers and such. Like is Manufacturing coming back, but in a different way, a way that violates sort of how we have structured these numbers to date.
Said in: Rolling Your Own Problems (Aug 9, 2026)Horizon: Evaluable continuously. The mechanism half is already settled (see below); the *claim* half — that the real industrial buildout outruns the manufacturing print — is readable through 2027–2028 by comparing construction employment (NAICS 23), information-sector employment (518210) and manufacturing payrolls (31–33) against announced data-center capex.Target: Dec 31, 2028Updated: Aug 29, 2026 (2 revisits)Confidence: Load-bearing, and the mechanism is confirmed rather than pending. Dan asked Claude on-mic to check whether trades sit inside the manufacturing number. They do not, definitionally: manufacturing is NAICS 31–33; electrical contractors are 238210 and plumbing/HVAC contractors 238220, both inside Construction (NAICS 23); operational data-center staff are 518210, inside Information. So data-center buildout labour can never appear in manufacturing payrolls regardless of framing. Context at recording: manufacturing employment showed "little change" over the 12 months to July 2026, sitting near 12.6M (FRED MANEMP), while the ISM manufacturing employment index crossed into expansion for the first time in 33 months. What remains genuinely open — and is the scoreable part — is whether the buildout is large enough, and domestic-hardware-heavy enough, to eventually show up in 31–33 via fabs and equipment manufacturing.
Didn'tDaniel (Sean endorses, reasoning from Meta's training investment)

A meaningful share of the construction-phase trades workforce on a large data center stays on permanently after commissioning — the headcount does not collapse to near-zero once the facility is running.

Resolution: Flagged 🔴 in the Ep 54 fact-check and the evidence has only hardened since. **Stargate (1 GW): ~6,400 construction workers → 100–1,000 permanent staff — 1.6% to 15.6%**, and the permanent roles are facility technicians and engineers, a different skill set rather than a retained construction crew. Hyperscale permanent staffing runs **0.2–0.3 people per MW** (against 2.0–3.0/MW at small 1–5MW sites), so a 300MW campus supports roughly 60–90 permanent people. Brookings (published 4 May 2026, updated 10 Aug 2026) found a county's first large data center raised data-processing employment **+56% over a decade** and telecoms +43% — but that is **only ~100–200 jobs**, with **wages unchanged** and home prices up just 2–5%. **The steelman the hosts didn't make, and it holds.** In Virginia, Texas, Ohio and Arizona the buildout is continuous enough that trades **chain from project to project for years**, so trades employment persists *regionally* even though almost nobody stays on any single site. If the claim is "the crew that builds it stays to run it," it is false. If it is "the work stays in the region," it is defensible — and Meta's training program guarantees *jobs*, not jobs at one site, which would satisfy the spirit while failing the letter. Score both readings as the entry originally asked. Sources: Brookings, Stargate reporting, Hamm Institute per-MW staffing. (2026-08-29)

Said in: Rolling Your Own Problems (Aug 9, 2026)Horizon: Evaluable as the 2025–2027 hyperscale cohort commissions — compare peak construction headcount against steady-state operations headcount per site, and watch whether trained cohorts are redeployed to new sites (which supports the *program* logic but falsifies the *permanence* claim).Target: Dec 31, 2027Updated: Aug 29, 2026Confidence: Load-bearing and currently trending wrong — flagged 🔴 in the episode fact-check, so this entry exists partly to be scored honestly later. Available evidence at recording: Meta's Hyperion campus in Louisiana peaks near 7,500 construction workers and settles at roughly 1,000 permanent jobs (~7.5:1); the Hamm Institute puts construction at 0.7–2.0 workers/MW against 1–2 permanent staff/MW at hyperscale; McKinsey puts up to 1,500 on-site for a 250,000 sq ft facility; crews typically demobilise after 12–36 months and move to the next project, which is the standing business model of construction trades. The "2,000 electricians" figure itself is a fair ballpark for a gigascale build — electrical is usually the largest single trade on these jobs — so the error is specifically about stickiness, not scale. The steelman the hosts did not make: Meta's training program guarantees *jobs*, not jobs *at one site*, so a permanently employed itinerant trades workforce would arguably satisfy the spirit of the claim while failing its letter. Score both readings.
PendingDaniel

Describing a personal AI agent you built — a "chief of staff" — becomes a standard, expected credential in job interviews across occupations, and the whiteboard interview spreads well beyond tech as employers move to test whether the candidate or the harness did the work.

Basically anyone should be coming into interviews, being able to talk about their own personal chief of staff that they have built and what it does for them." (On verification): "I don't need you to show me on my phone. I need you to get up on that whiteboard and show me the architecture of what you're thinking. … Or did the harness do it for them?
Said in: Rolling Your Own Problems (Aug 9, 2026)Horizon: 2–3 years. Evaluable mid-2028 through hiring-practice surveys, the appearance of agent-portfolio prompts in standard interview guides, and whether whiteboard/architecture rounds appear in non-technical hiring (Dan's own examples: electrician, banker, teacher, nurse).Target: Dec 31, 2028Confidence: Load-bearing on the mechanism, speculative on the timeline. Dan's argument is that firms without training pipelines — unlike Goldman or Morgan Stanley, which run whole divisions for ingesting juniors — will substitute demonstrated self-tooling for the training they cannot afford. Sean pushes back usefully twice: that this may be confined to knowledge work, and Dan answers with the plugged-in-electrician analogy; and that regulated fields (nursing on Epic, banking on the Microsoft stack) will lag badly on the professional side even if the personal side arrives. Score the regulated-sector carve-out separately — Dan concedes it on air. Sean's "my chief of staff is named number one" is the first on-mic naming of his own agent stack.
OverdueDaniel

The 2025–2026 layoff wave is mostly the unwinding of 2021 overhiring and "fake jobs," not AI displacement; AI is a small contributor being used as the cover story, and more of that unwind is still to come.

I think we've seen, you know, the overhiring in twenty twenty one and then AI being the cover story for the layoffs that we've seen last year and this year. and I really don't think AI is a big part of it. I think it is a small part of it. I think most of it was just over hiring and and fake jobs. and we're gonna see a lot of that. We're already seeing a lot of that.
Said in: Rolling Your Own Problems (Aug 9, 2026)Horizon: 12–24 months. Evaluable via layoff attribution studies, WARN-notice sector mix, and whether headcount stabilises at pre-2021 trend rather than continuing to fall as AI capability rises. A clean falsifier: sustained payroll declines concentrated in roles with demonstrated AI substitution, while over-hired functions have already normalised.Was due: Dec 31, 2021Confidence: Load-bearing and unusually falsifiable for a labour claim, because it makes an *attribution* rather than a direction call. Context at recording: the July 2026 print (released 2026-08-07) showed payrolls −23,000 against consensus near +83,000, with May and June revised down a combined 103,000 — so the deterioration is real and the disagreement is only about cause. Note the tension with `ai-deflationary-except-compute` from the same episode: Dan argues AI is powerfully deflationary *and* barely responsible for job losses, which is coherent (productivity gains absorbed as output rather than headcount) but worth holding him to.
PendingDaniel (Sean has been a proponent of more trade jobs "for a while," and endorses)

The cultural and economic swing back toward skilled trades overshoots — having pushed too far toward universal college, the correction lands harder than a smooth rebalancing would.

A whole lot of people would rather be working with their hands and but they were told from birth that like you're not supposed to work like that and you're supposed to go to school and do the other thing. And the pendulum swung one way too far and it's gonna swing a little bit hard on the way back.
Said in: Rolling Your Own Problems (Aug 9, 2026)Horizon: 3–5 years. Readable through trade-school enrolment growth rates against four-year enrolment, apprenticeship registrations, and trades wage growth relative to entry-level knowledge work. "Overshoot" needs a threshold to score: trades enrolment growth outrunning trades job growth badly enough to compress the wage premium.Confidence: Directionally load-bearing, casual on magnitude, and the hardest entry in this batch to score cleanly because "too far" is undefined. Supporting context at recording: US fertility at a record-low 1.599 (2024), public K-12 enrolment down from 50.8M (2019) to 49.4M (2024) and projected below 47M by 2030, and confirmed 2025–26 elementary closures across California, Iowa, Arizona and Texas — the demographic pipeline for four-year colleges is genuinely shrinking. Against it: national college enrolment rose ~1% in fall 2025 (+187,000, NSC), which is the opposite of the collapse the hosts assumed, and Sean's specific University of Arizona figure conflated a ~23% *freshman* decline with total enrolment (down ~2.7%). So the premise the prediction rests on was partly mis-stated on air even though the demographic trend behind it is real.
PendingSean (Dan supplies the architecture requirement and the lock-in argument)

The agent interface becomes the operating system — the primary layer through which people touch every other tool — and it must be a *horizontal* layer that survives changes of model provider and harness, not a vertical stack per vendor.

Said in: Rolling Your Own Problems (Aug 9, 2026)Horizon: 3–5 years. Evaluable on whether the durable winners at the interface layer are provider-agnostic (Buzz's model-agnostic design, workgroove, HQ) or vendor-native (Claude Tag, Cowork, Copilot), and on whether users report an agent as their primary computing interface rather than one app among many.Updated: Aug 29, 2026Confidence: Load-bearing thesis, and the episode's most testable *product* claim because both hosts already have skin in it. Sean's own evidence cuts against the horizontal preference: Cowork's mobile release (2026-07-07) obsoleted several tools he had built precisely to stay provider-agnostic, and he says out loud that the vendor-native version is "pretty slick" and he may just use it. Dan holds the line anyway and names the risk from the other direction — "you do doing feature releases that just sort of bulldozed something that you had built." The named contenders at recording: Buzz (Block, announced 2026-07-21, Apache-2.0, agents as first-class channel members over Nostr, pre-1.0), workgroove.ai, HQ. Pairs with `automation-agency-window-closing` and Ep 53's `agent-ready-commerce` lane.
PendingDan (Sean endorses)

Skilled-trades labor remains in structural undersupply for data-center buildout from now through at least 2030, plausibly to 2040; only a deliberate policy mistake or demand collapse interrupts.

Said in: Gone Building (May 31, 2026)Horizon: Evaluable annually 2027–2030; full call resolves end of 2030Target: Dec 31, 2030Updated: Aug 29, 2026 (5 revisits)Confidence: Load-bearing — extends the `atom-economy` build-window thesis with a sharp date claim. Indianapolis ($55/hr) → Minneapolis ($80/hr) labor-migration anecdote as the supporting data point.
PendingDaniel (in response to Sean's question)

AI tool adoption will compress the labor-arbitrage advantage for Philippines-based remote workers within 5 years — particularly in design and content roles vulnerable to gen-AI — forcing skillset upskilling or wage compression.

Said in: Managing Remote Teams, Walmart v. Amazon (May 12, 2024)Horizon: 5 years (by 2029)Target: Dec 31, 2029Updated: Aug 23, 2026Confidence: Medium
PendingDaniel (Sean moves toward it on-mic but explicitly reserves judgment)

Warsh's reduced transparency — fewer FOMC meetings, less telegraphing, a Fed that is harder to read — is a deliberate strategy to *protect* Fed independence rather than an erosion of it; he is an antagonist to Fed convention, not to the institution.

I think everyone's up in arms about how this is ruining Fed independence. And I'm kind of thinking it's protecting the Fed. … He might be an antagonist, but he's an antagonist to how things have been done, not to the actual institution itself. … I don't believe Warsh wants that. I think he wants to not completely be understood. Like this isn't a mistake is what I'm trying to say.
Said in: It's Memes that Keep Us Together (Aug 2, 2026)Horizon: Evaluable across Warsh's term (to 2030). First real read: whether the meeting-cadence change is adopted, and whether the Fed's rate path over 2027 tracks the data rather than executive pressure. Falsified if the opacity turns out to serve political accommodation — e.g. cuts arriving without a data case for them.Target: Dec 31, 2030Updated: Aug 29, 2026 (4 revisits)Confidence: Load-bearing — the contrarian thesis of the episode's first act, and the reframe that moves Sean off his position. Both hosts explicitly hedge: Dan "I retain the right to change my mind"; Sean "I reserve final judgment." Context at the time: July 28–29 FOMC held at 3.50–3.75% on a 9–3 vote with three hawkish dissents; the NYT broke the 6+2 meeting proposal on July 31.