7 reads.
Boris Cherny♥ 3.8k
Boris Cherny on living inside Artifacts: visual explanations of tricky code, system diagrams, dashboards he shares with the team, all built from the session at a private link. The signal here is a power user telling you which everyday habit actually changed how he works. Small feature, big workflow shift.
Marc Andreessen 🇺🇸♥ 5.8k
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.
Block♥ 1.4k
Block's numbers on their internal agent system are the ones to quote in an argument. Engineers tag it in Slack, it researches, plans, and ships: 200,000 operations a day, 1,500 PRs merged a week, 15% of all production code. This is what agents coordinating across a real codebase looks like at scale, not in a demo.
brryant♥ 921
A launch pitch dressed as a provocation: AI is making marketers lazy, so make the website do the work instead. Mostly a product announcement with a $27M seed behind it, but the underlying bet, that the site itself becomes an active agent rather than a brochure, is where a lot of marketing tooling is heading.
Paul Bakaus♥ 494
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.
Khairallah AL-Awady♥ 2.5k
A shared full guide to shipping your first agent, with the pitch that it collapses a two-week slog into a day. Standard on-ramp material, but a decent starting point if you're going zero to one and want a single path instead of ten browser tabs.
Avi Chawla♥ 3.4k
Karpathy's line, put to work: stop being the bottleneck, put in few tokens, have a huge amount happen on your behalf. The framing is that loop engineering is the mechanism that actually delivers that. A quick nudge toward the mindset shift, not a how-to.