Read these first.
TSMC Risk (Stratechery Article 1-26-2026)
Why it matters
Ben Thompson argues the main TSMC risk for AI is not just Taiwan geopolitics but TSMC’s conservative capacity expansion: Amazon, Microsoft, Google, and Meta all said in late-2025 earnings that AI demand still exceeds supply, and TSMC CEO C.C. Wei explicitly said the bottleneck is "silicon from TSMC," not power, cooling, racks, or turbines.
Key details
- TSMC’s underinvestment predates the current shortage: after a large 2021 capex increase tied to COVID shortages and 5G expectations, annual capex was essentially flat and even declined year-over-year in 2023 and 2024, despite ChatGPT’s November 2022 launch triggering a hyperscaler AI spending surge.
- TSMC is now raising capex, but on a lag that matters for AI buildout timing: 2025 capex rose 37% to $41 billion, and 2026 guidance is $52-56 billion (about $54 billion midpoint, up roughly 32%), yet Wei said new fabs take 2-3 years to build, meaning little effect in 2026, only some effect in 2027, and significant capacity mainly in 2028-2029.
- Wei framed TSMC’s stance as rational foundry risk management: because foundries are overwhelmingly capex-driven businesses, overbuilding can turn high-margin revenue into years of depreciation, weak pricing, and potentially "a big disaster," so TSMC is effectively offloading demand-risk onto hyperscalers and fabless chip firms.
Brief
Ben Thompson’s January 26, 2026 Stratechery essay reframes “TSMC risk” away from the familiar Taiwan-invasion narrative and toward a more immediate economic bottleneck: TSMC’s monopoly position and conservative capital allocation are constraining AI infrastructure growth. He ties together hyperscaler earnings commentary from Amazon, Microsoft, Google, and Meta, all of which reported that AI demand still exceeds supply, with TSMC CEO C.C. Wei’s own admission that the limiting factor is chip output rather than electricity, cooling, or other data-center inputs. That matters because it suggests the practical bottleneck in the AI buildout is at the foundry layer, not the grid or server deployment layer many observers focus on.
The article’s central evidence is the mismatch between hyperscaler capex acceleration after ChatGPT’s November 2022 debut and TSMC’s comparatively flat capex in 2023-2024. TSMC is now responding—2025 capex rose to $41 billion and 2026 guidance is $52-56 billion—but Wei says fabs take two to three years to come online, so meaningful relief arrives mostly in 2028-2029. Thompson argues this is rational from TSMC’s perspective because foundries bear enormous fixed-cost risk, but irrational for the ecosystem because it shifts the downside onto customers that lose revenue when demand cannot be served. His strategic conclusion is that hyperscalers and fabless chip firms should absorb the pain of qualifying Samsung or Intel as real alternatives; only credible foundry competition, he argues, will force more aggregate capacity investment and reduce both economic and geopolitical concentration risk.
Deeper context and second-pass items.
Anthropic's agent harness reportedly includes an 823-line retry system (claimed…
Why it matters
Anthropic's agent harness reportedly includes an 823-line retry system (claimed by @rohit4verse in a post dated 2026-04-07).
Key details
- Claude Code's source is said to span 55 directories and 331 modules; the author says he analyzed all 331 modules to build an agent harness.
- Author claims his teardown saves the ~six months most agent teams would spend rediscovering Claude Code; post engagement: 387 likes, 26 retweets, 12 replies.
Brief
Anthropic's agent harness reportedly contains an 823-line retry system, according to @rohit4verse's April 7, 2026 post. He says Claude Code's public source spans 55 directories and 331 modules and that he reverse-engineered all 331 modules to build a harness—claiming this saves the typical six months teams spend rediscovering production agent architecture.
Fast scan items.
Used Claude Code for 3 months and manually fixed mistakes every day until…
Why it matters
Used Claude Code for 3 months and manually fixed mistakes every day until discovering Hooks; a 10-minute setup made those routines automatic.
Key details
- The author highlights 8 Claude Code Hooks that automate common oversights—examples include enforcing code formatting, preventing edits to specified files, and running tests before finishing.
- Posted April 3, 2026 on X (https://x.com/zodchiii/status/2040053353967747440) with 6,318 likes, 276 retweets, and 92 replies.
Brief
@zodchiii reports using Claude Code for three months while manually correcting its mistakes daily until discovering Claude Code "Hooks." After a brief 10-minute setup, eight hooks automated recurring steps—such as enforcing formatting, protecting files, and running tests—turning previously manual checks into an automated routine. The April 3, 2026 tweet (6,318 likes, 276 retweets, 92 replies) emphasizes the productivity change.
Claude bills by tokens, not message count—token growth per conversation follows S…
Why it matters
Claude bills by tokens, not message count—token growth per conversation follows S × N(N+1) / 2 (S = avg tokens/exchange, N = message count). At ~500 tokens/exchange this yields ~7,500 tokens for 5 messages, ~27,500 for 10, ~105,000 for 20, and ~232,000 for 30 (message 30 ≈ 31× cost of message 1).
Key details
- Practical habits to cut token spend: edit your original prompt and regenerate (replaces history), start a new chat every 15–20 messages (or ask Claude to summarize + paste into new chat), batch multiple questions into one message, upload recurring PDFs to Projects (cached, not re-tokenized), and save Memory/User Preferences to avoid repeating setup messages.
- Model and feature choices matter: use Haiku for simple tasks (author reports it can free up ~50–70% of budget vs Sonnet/Opus), turn off Search/Tools and Advanced Thinking when not needed, and pick model tiers by task (Haiku=low, Sonnet=medium, Opus=high).
- Usage management: Claude uses a rolling 5-hour window; starting Mar 26, 2026 peak weekday hours (5:00–11:00 PT / 8:00–14:00 ET) deplete session limits faster. Pro, Max 5x and Max 20x subscribers can enable “Overage” (pay-as-you-go API billing) with a monthly spending cap as a safety net.
Brief
Author 0x_kaize (posted 2026-03-29, 10,819 likes / 1,618 retweets / 213 replies) argues that Claude’s perceived strictness comes from token accounting rather than message count and lays out ten tactical habits to cut token spend. Key technical points: token cost scales quadratically with message count (S × N(N+1)/2) with concrete examples at ~500 tokens/exchange; edit original prompts instead of sending follow-ups; start new chats every 15–20 messages or paste a summary into a fresh chat; batch multiple tasks into one message; upload recurring files to Projects so they’re cached; and save Memory/User Preferences to avoid repeating setup. The post also recommends Haiku for low-cost tasks (claiming 50–70% budget savings versus Sonnet/Opus), disabling unused tools, spreading work across the rolling 5-hour window, avoiding peak hours (change effective Mar 26, 2026), and enabling overage for paid plans as a safety net.
Lower-priority archive.
The International Space Station averages about 600 Mbps internet (per…
Why it matters
The International Space Station averages about 600 Mbps internet (per @pronounced_kyle's 2026-04-07 post).
Key details
- South Pole connectivity is roughly 25 Mbps; Antarctic stations decline Starlink to preserve RF‑quiet operations.
- The post also mentions an Orion capsule (330‑cubic‑foot) carrying four astronauts who, over the prior six days, traveled farther from Earth than any humans; engagement: 107 likes, 4 retweets, 7 replies.
Brief
Pronounced_kyle's 2026-04-07 X post contrasts connectivity: the ISS averages ~600 Mbps versus ~25 Mbps at the South Pole, where operators avoid Starlink to maintain RF‑quiet conditions. The thread also references an Orion capsule (330‑cubic‑foot) carrying four astronauts who, in the previous six days, traveled farther from Earth than any humans, and the post recorded 107 likes, 4 retweets, and 7 replies.
Graham Duncan (co‑founder of East Rock Capital) introduced the phrase “time…
Why it matters
Graham Duncan (co‑founder of East Rock Capital) introduced the phrase “time billionaires” on the Tim Ferriss podcast in March 2019, contrasting a financial billionaire with someone who has ~1 billion seconds (~31 years) of life remaining.
Key details
- Time conversions Duncan cites: 1 million seconds ≈ 11 days; 1 billion seconds ≈ slightly over 31 years; a 20‑year‑old has ~2 billion seconds left, a 50‑year‑old ~1 billion seconds.
- Concrete examples Duncan used: Rupert Murdoch (~$20 billion, age 87) as someone with lots of capital but far less remaining time; Tim Urban’s life‑calendar poster (52 weeks × 90 rows) was cited to visualize finite life weeks.
- Investment implication: young investors should treat time as their competitive advantage — long horizons enable compounding, patience, emotional resilience, and the ability to recover from mistakes; you can’t sell future years at the end of life, you must sell them now.
Brief
Graham Duncan’s “time billionaire” metaphor (shared on Tim Ferriss’ March 2019 podcast and reposted by APompliano on 2026‑04‑06) reframes wealth as life‑time rather than dollars: 1 million seconds ≈ 11 days and 1 billion seconds ≈ ~31 years, so a 20‑year‑old has roughly 2 billion seconds to compound. Duncan contrasts money billionaires (he cites Rupert Murdoch, ~$20B at age 87) with those who possess long horizons, and references Tim Urban’s life‑calendar poster (52 weeks × 90 rows) to visualize scarcity. He argues the practical investing takeaway is to lean into time: decades allow patient capital, stronger emotional control, recovery from errors, and superior compound returns. The piece also invokes the 2011 film In Time to illustrate time‑as‑currency and notes you can’t sell years at life’s end — you must monetize time while you have it.
A tweet by @loshmi on 2026-04-07 says people found $6,000 (in 4 minutes), $70,000…
Why it matters
A tweet by @loshmi on 2026-04-07 says people found $6,000 (in 4 minutes), $70,000 (from a job left in 2016), and $763,000 (from a deceased parent) using a free government unclaimed‑funds database.
Key details
- The post warns that third‑party tools like OwedToYou.ai charge fees for finding certain categories of unclaimed money even though the government database is free; the tweet had 2,453 likes, 88 retweets, and 66 replies.
Brief
The tweet by loshmi on 7 April 2026 reports people finding unclaimed funds via a free government database — $6,000 in four minutes, $70,000 tied to a job left in 2016, and $763,000 from a deceased parent. It warns that third‑party services like OwedToYou.ai charge for searches available for free and urges readers to check their names.