17 reads.
Andreessen's long, unusually good essay reframing SpaceX as the one company assembling the full stack for a post-scarcity future: cheap launch, orbital compute, lunar industry, Mars. The engineering-culture sections carry it, especially Musk's five-step Algorithm and the idiot index. Not AI-specific, but the orbital-data-center thesis ties directly to where compute and energy are heading. A real sit-down read.
A neat idea made real: a feedback loop that catches visual slop and design-system drift while the agent builds, instead of after. It turns design consistency from a thing you ask for into a hook that runs automatically. If your agents produce frontends that look slightly off every time, this is the missing guardrail.
The best long read on why a top-tier model isn't the point. The system around it is. Loops, memory, verifier sub-agents, and state files are what make each run leave the next one smarter, and the piece lays out the whole stack with cost-routing advice for when to reach for the expensive model versus a cheap one. Long, but it's the map most people are missing.
Steinberger's minimal recipe: an orchestrator that wakes every five minutes and directs work to threads, combined with triage, auto-review, and computer-use skills so work lands on its own. The takeaway is how little scaffolding a useful loop actually needs once you have sharp skills to call. Concrete and copyable.
An Anthropic engineer on two things the top model changes: self-correction loops and memory. The sharpest takeaway is that the model shouldn't grade its own work. An independent verifier explores harder and recovers from dead ends where self-critique stalls at good enough. Short, concrete, and from someone who actually ran the experiments.
The best explainer on the phrase everyone was repeating without defining. A loop is cron plus a decision-maker in the body: the model, not a hardcoded script, picks the next move each tick. The punchlines land, that the loop, not the model, is now the expensive part, and that the real asset is the skills a loop calls, not the loop itself. If you read one thing on loops, this.
A plain-English tour of the Claude features hiding in plain sight: Projects, memory, extended thinking, scheduled tasks, prompt caching, custom roles. Nothing exotic, but the value is in the framing. Each one takes minutes to set up and pays off daily. Good to forward to anyone still treating Claude as a fancier search box.
An honest field report: dynamic workflows felt useless until they were pointed at adversarial review. The move is splitting a review into thin, mean, single-focus lanes, correctness, duplication, safety, each agent required to bring a way to verify its own finding. It beats self-review because the model likes its own work too much. The step-by-step is copy-and-adapt ready.
Anthropic's own writeup on building agents that do data analysis. The useful parts are the unglamorous ones: skills, clean data foundations, and evaluations. If you're wiring an agent into real business numbers, this is the part everyone skips and then regrets.
The line most people skim: every agent in a workflow can run a different model. This is the proof. A 33-agent audit, cheap readers plus one smart synthesizer, ran in under five minutes and found a real buried error. Put the expensive model where the thinking happens and run the rest on the cheap one. That's the economics of parallel agents in one example.
A clean way to think about agent design: the model is deliberately thin, and intelligence gets pushed outward into memory, skills, and protocols that the harness composes at runtime. The useful question it hands you is where any new capability should live. Good conceptual scaffolding if agents still feel like a bag of tricks.
The canonical piece on dynamic workflows, from the Anthropic engineer who built them. Claude writes its own custom harness on the fly to beat the failure modes of one long context window: laziness, self-preference, goal drift. The example prompts alone are worth the read, and it names the reusable patterns (fan-out, adversarial verify, tournament) you'll see everywhere else. Start here.
A design studio's field report on a real shift: the deliverable is no longer a PDF brand guide but a folder of structured files an agent can build from. The value moves upstream to the thinking, and the sharp bit is what they call magic_trick.md, the one human, left-of-center idea the system can't generate on its own. Best essay here on where human creativity stays scarce.
A pointed demo of where the moat isn't: someone cloned the core of two heavily funded legal-AI products in two weeks and open-sourced it. The argument, that firms should own their application layer instead of renting it forever, is the uncomfortable question every vertical SaaS company is now facing. Provocative, and hard to dismiss.
A genuinely good step-by-step on running Claude Code 24/7 on an always-on Mac Mini so you can text it tasks from anywhere. The best detail is the one nobody mentions: there's no message queue, so a sleeping laptop drops everything, which is the whole case for dedicated hardware. Practical if you want a personal agent that never goes dark.
A crisp reminder of what belongs in your project config. Most hand-written setup was stuff the agent can discover by reading the code. The new approach keeps only what Claude would get wrong without it: security rules, mandatory workflows, non-obvious gotchas. Delete the rest. 458 lines to 68.
The reference for anyone configuring Claude Code seriously. It walks the whole control center: CLAUDE.md, path-scoped rules, and hooks, with the key nuance that instructions are suggestions but hooks are deterministic. Keep CLAUDE.md under 200 lines or adherence drops. This is the one to bookmark.