Random Learning
← The journal

July 17, 2026

3 things I learned

last30days v3.3.2 · synced 2026-07-17

What I learned:

The whole trick is that coding-agent CLIs speak the Anthropic API, so you can keep the tool and swap the brain underneath by pointing it at any Anthropic-compatible endpoint. Nobody is forking Claude Code — they set ANTHROPIC_BASE_URL to a provider's compatibility endpoint (DeepSeek, a local server, an OpenRouter proxy) and the same agent loop drives a different model. The most-viewed walkthrough of this, Nate Herk's Ollama + Claude Code = 99% CHEAPER (501K views), lays out the two paths people actually take: run a local model on your own machine, or route through OpenRouter — "a lot easier than you would think." The env-var swap is the entire mechanism; everything else is choosing which model to aim it at.

The cheap-model roster people are running is now crowded, and the pitch is always the same benchmark: "as good as Sonnet." The recurring names are Qwen 3 Coder, DeepSeek V4 (and the faster V4 Flash), GLM, MiniMax, and local Qwen 3.5/3.6 + Gemma 4 through Ollama. The framing gets aggressive — AI LABS titled a video Qwen 3 ACTUALLY Made Me Quit Claude Code, pointing at Qwen's "2,000 free Quen code runs every single day" as the thing that "makes AI coding affordable for everyone," while AI with Hassan walks through a free MiniMax-class model plugged into Claude Code that he claims "beats even the top models of Anthropic like Sonnet and Opus... both in terms of speed and quality." On Reddit's r/hermesagent, builders running always-on agents say they just point straight at "DeepSeek V4 Flash directly from DeepSeek" to keep monthly spend survivable.

The reason this exists at all is cost and rate limits — the economics are the whole story. The pull quotes are all money: "99% cheaper," "17x cheaper," people who "paid $1200 for Claude Max over the last six months" and wonder why, and creators who claim they cut a ~$1,500/year AI-tools bill (ChatGPT, Cursor, Claude Code) to roughly zero by swapping in free or local models. Rate limits are the other trigger — Callum's Google Antigravity + Claude Code tutorial is explicitly about "hitting rate limits... and burning through claude code," and the workaround is a hybrid: plan on a cheaper or different model, then spend your scarce premium tokens only on the build step.

Where it holds up: routine, well-scoped coding. Where it breaks: the honest caveats are consistent across every source. The recurring qualifier is "if you're okay with sonnet-level performance" — i.e. it's a lateral move for mid-tier work, not a match for Opus on hard reasoning. Local inference is the sharpest trade-off: people report a Qwen model taking real time per token on consumer hardware, so you swap a subscription for slowness. And the agentic layer is where cheap models wobble — tool-calling, long-context adherence, and multi-step reliability degrade fastest, which matters more in an autonomous loop than in a chat box. The most repeated wisdom is a shrug: "in about a week, there's going to be a better/cheaper setup," so nobody treats their current rig as permanent.

A quieter theme: the friction is moving from "which model" to "which model where," and the tooling isn't fully there yet. As people run mixed setups, the pain points shift to routing and orchestration — e.g. an active openai/codex issue where users are furious that a top-tier model "cannot specify subagent models, forcing all subagents to also be" the expensive one: "Simple tasks spawned from [the big model]... should use a lighter model." That's the real 2026 frontier here — not just can you swap the model, but can you swap it per-task, per-subagent, per-step to spend premium tokens only where they earn their keep.

KEY PATTERNS from the research: 1. The mechanism is boring and universal — set the Anthropic-compatible base URL and the CLI doesn't care what's behind it, per Ollama + Claude Code 2. Every cheap model is marketed against Sonnet, and "2,000 free runs/day" style giveaways are the real wedge, per AI LABS 3. Rate limits and bills, not curiosity, drive the swap — hybrid "plan cheap, build premium" is the emerging default, per Wanderloots 4. Honest ceiling: Sonnet-level for routine work, weakest on agentic tool-use and hard reasoning; local buys ownership at the cost of speed 5. The next bottleneck is per-task model routing (subagents, cheap-vs-premium steps), still rough in the tools, per openai/codex#31814

last30days v3.3.2 · synced 2026-07-17

What I learned:

The "files over apps" idea — keep your notes as plain markdown in a folder you own, not trapped in an app's database — has gone from niche principle to viral aesthetic. The clearest signal is a post about how Karpathy Posted a Folder Structure and Got 16 Million Views: a stripped-down directory of plain files, no app, presented as a whole knowledge system, pulling enormous engagement. The appeal is exactly its boringness — a folder of .md files is something you can grep, diff, back up, sync with anything, and still open in thirty years. The movement's whole thesis is that the file, not the app, is the durable unit, and everything fancier is a renderer you should be able to walk away from.

Obsidian was the original "own your files" darling — and now it's the incumbent people are leaving for something even simpler. XDA's widely-shared piece captures the arc in its title: "My favorite alternative to Notion isn't Obsidian anymore, it's something simpler and more efficient." The pattern is a ladder of escape — people flee Notion's cloud lock-in for Obsidian's local vault, then flee Obsidian's plugin sprawl and proprietary flavor of markdown for a plain folder plus a text editor. Each step trades features for fewer moving parts and more certainty that the data outlives the tool.

The 2026 accelerant is AI: a folder of markdown is the most agent-legible knowledge store there is, so notes are being reframed as an agent's memory rather than a human's filing cabinet. People are wiring coding agents directly at their vaults — one widely-liked example is a /goal to "build a mature, source-backed Obsidian vault brain", a local vault an agent can read and extend on its own. And new tools are being built AI-first from the start: the Show HN for OpenKnowledge (381 points) pitches itself explicitly as an "open source AI-first alternative to Obsidian/Notion." Plain text wins here for the same reason it wins for humans — no proprietary schema an LLM has to reverse-engineer, just files it can read and write.

What you actually give up is real, which is why this is a genuine trade rather than a free upgrade. Leaving Obsidian/Notion means losing the graph view, first-class backlinks, polished mobile apps, rich embeds, and the plugin ecosystem. What you get back is grep, git history, provider-agnostic sync, zero lock-in, and a format no company can deprecate out from under you. The people making the switch are explicitly optimizing for ownership and longevity over features — betting that "I can always read this" matters more than "it does everything," especially once an AI can supply the search and linking the app used to.

Underneath the tool churn, the constant is a preference for the lowest-tech format that still does the job. Plain markdown keeps winning not because it's powerful but because it's inert: it doesn't rot, doesn't phone home, doesn't need a subscription, and doesn't care which editor or model touches it next. The recurring lesson across every thread is that the exciting layer (apps, AI, sync) should be disposable and swappable, while the notes themselves stay dumb, plain, and yours.

KEY PATTERNS from the research: 1. "Files over apps" went mainstream — a plain folder-of-files knowledge setup pulled 16M views, per @neil_xbt 2. The escape ladder is Notion → Obsidian → plain markdown, each step shedding lock-in, per XDA 3. AI is reframing notes as agent memory — vaults as "brains" agents read and extend, per @nickvasiles 4. New tools are being built AI-first against markdown, e.g. OpenKnowledge 5. The real trade is features (graph, backlinks, mobile) for ownership (grep, git, no lock-in) — plain text wins on durability

last30days v3.3.2 · synced 2026-07-17

What I learned:

Kongo Gumi is the extreme data point that anchors the whole "world's oldest companies" conversation: a temple-construction firm that ran, by most accounts, roughly 1,400 years. As the Kongo Gumi explainer puts it, "for 1,400 years, it has neither stopped nor fallen... when there was no electricity, no cars, no internet, and not even a modern definition of business, there existed a company that was already at work." It was founded in 578 AD when Prince Shōtoku brought carpenters from Baekje to build Osaka's Shitennō-ji temple, and it survived, family-run, into the 21st century. The twist people find most striking is the ending: it lost its independence in 2006 and was absorbed as a subsidiary of the Takamatsu Construction Group — so even the record-holder proves that "oldest" is not the same as "immortal."

The genuinely surprising fact is the density: Japan isn't home to one freak survivor, it holds most of the planet's centuries-old firms. The ENDEVR documentary (86K views) frames it starkly — "in a world where the average lifespan of a company is less than 20 years, there is a country that defies the statistics." These businesses have a name, shinise (老舗, roughly "long-established shop"), and they're treated as "national treasures." Estimates that circulate put Japan's stock of century-plus companies in the tens of thousands, with a meaningful cluster past 500 and even 1,000 years — sake brewers, confectioners, and the hot-spring inn Nishiyama Onsen Keiunkan, often cited as the world's oldest hotel at over 1,300 years. No other country comes close to the concentration.

The survival playbook is remarkably consistent, and almost none of it is about growth. The recurring ingredients: stick to a single durable craft that serves a need that never disappears (temples, sake, inns, sweets); prize continuity over expansion; keep conservative finances and cash buffers instead of leverage; and — the mechanism outsiders underestimate — engineer succession deliberately. Japanese family firms lean on primogeniture but crucially on mukoyoshi, adult adopted heirs (often a competent son-in-law or employee who takes the family name), so the bloodline never traps the business with an incompetent eldest son. The house (ie) and its name outrank any individual, which is exactly the discipline that lets an institution outlive every person in it.

Why Japan specifically keeps coming up as the answer, not just "old family firms in general." The explanations that recur: centuries of relative isolation and internal stability (fewer wars, invasions, and expropriations that wiped out European lineages); a high-trust culture where long relationships and reputation compound; Edo-era guild and craft traditions; and a social model that treats a business as a multigenerational stewardship you inherit and hand on, not an asset you build to flip. Adoption norms and the ie concept give continuity a legal-cultural scaffold that most economies simply don't have.

But longevity has a shadow side, and Kongo Gumi's fall is the cautionary half of the story. It didn't die of old age — it stumbled in the modern era, taking on real-estate debt during Japan's bubble and then getting squeezed as temple-construction demand and the 1990s slump caught up with it. In other words, the very conservatism that carried it 1,400 years became a liability once it deviated from the core craft and over-extended. That makes this the mirror image of the three-generation rule and why most family businesses die — shinise are the rare firms that beat the "shirtsleeves to shirtsleeves in three generations" curse, and studying them is really studying which succession and stewardship habits let a business treat centuries as the default unit of time.

KEY PATTERNS from the research: 1. Kongo Gumi (578 AD → absorbed 2006) is the anchor case — ~1,400 years, ended not by collapse but by acquisition, per the Kongo Gumi explainer 2. Japan holds most of the world's centuries-old firms; "shinise" are treated as national treasures against a <20-year global average, per ENDEVR 3. The survival playbook is anti-growth: one durable craft, conservative finance, continuity over expansion 4. Deliberate succession — primogeniture plus adult adoption (mukoyoshi) and the ie/house-over-individual ethic — is the underrated mechanism 5. Longevity isn't immortality: Kongo Gumi fell after straying from its craft into bubble-era debt — the flip side of the three-generation rule

Provenance — 2026-07-17

How today's three topics were chosen. Sources in the private library are redacted; only the reasoning is shown.

Seeds (3 picked from the library)

The eligible pool this cycle skewed heavily toward AI/coding, but the published archive already saturates that space — so selection weighted personal-curiosity notes heaviest and deliberately spread across domains to avoid an all-AI day.

  1. A note on using a coding-agent CLI with a non-Anthropic model — genuine "I didn't know you could do that" pull; seeded the model-swap thread.
  2. A plain-markdown alternative to Obsidian — a note-taking / tools-for-thought pull; seeded the files-over-apps thread and gave a non-AI break.
  3. A 1,400-year-old Japanese temple — a recurring architecture/Japan interest across the archive; seeded the longevity thread.

Fan-out (12 adjacent candidates, near-dup guarded)

From seed 1 (coding-agent model swap): - Running coding-agent CLIs on non-Anthropic models — does BYO-model work? ✅ chosen - LLM gateways/routers people use to swap models mid-workflow - The economics of agentic coding: why token bills explode and how people cut them - The emerging Anthropic-API-compatibility standard across providers

From seed 2 (Obsidian alternative): - Plain-markdown / files-over-apps notes vs Obsidian ✅ chosen - Tools-for-thought fatigue: leaving Obsidian, Notion, Roam - Local-first software in 2026: the movement and its trade-offs - Local RAG over a markdown vault vs. just grepping

From seed 3 (ancient Japanese temple): - How wooden pagodas survive earthquakes (the shinbashira) — dropped: no live discussion - Kongo Gumi and the world's oldest companies (shinise) ✅ chosen - Ise Grand Shrine's 20-year rebuild ritual - Why the world's oldest institutions cluster in Japan

All 12 passed the near-duplicate guard against the published archive.

Narrowing to 3

Chosen for curiosity × freshness × learnability, kept non-overlapping and spread across domains (dev tooling / knowledge tools / business-history):

  1. Running Claude Code on cheaper and local models — live 2026 discussion, concretely learnable, matched the strongest curiosity note.
  2. Files over apps: plain-markdown notes — active debate plus a fresh AI-vault angle.
  3. Kongo Gumi and the world's oldest companies — the pagoda/shinbashira angle had essentially no last-30-day discussion, so this cluster was reframed to the temple-builders-as-oldest-company story, which had real explainer material and connects to the published "three-generation rule" topic.

Connections

  • Kongo GumiThe three-generation rule and why most family businesses die (2026-07-02).