I built "zero2claude", a free course that takes people from zero terminal experience to shipping with Claude Code. The curriculum goes from absolute zero → software basics → Claude Code fundamentals → advanced usage. No shortcuts, no assumptions. 17,000 students. 7 languages. ~500 active hourly. No marketing. No ads. Pure word of mouth. The entire platform? Built and operated by one person with Claude Code. Lighthouse audit: ✅ Performance : 96 ✅ Accessibility : 100 ✅ Best Practices : 100 ✅ SEO : 100 Production stats: ~6.4M requests/day. 74 req/sec sustained. <0.003% error rate. Claude Code doesn't just write code. It builds production-grade, scalable products. The best way to grow Claude Code adoption isn't to simplify the tool. It's to level up the people. Give fishing rods, not fish. Free. No paywall. My contribution to the community. Link in the comments 👇

Personal update: I've joined Anthropic. I think the next few years at the frontier of LLMs will be especially formative. I am very excited to join the team here and get back to R&D. I remain deeply passionate about education and plan to resume my work on it in time.

Joined a new AI-native company this week and it’s kind of wild how different it feels already. The laptop arrived, I logged in, and an agent basically took over from there. It set up my dev env, pulled repos, fixed dependency issues, got permissions approved, pointed me at the backlog, linked the architecture docs, and surfaced the Slack debates I actually needed to read before touching production. When I needed context on something, I asked the agent and it found the exact thread from months ago explaining why a decision was made, who owned it, the related Linear issues, and the PRs connected to it. I’ve only been here 3 days but it honestly feels like I’ve worked here for a year because the usual friction and scavenger hunt for context just isn’t there anymore. We should probably stop calling this “onboarding” and rename it to “mounting” because this feels a lot more like mounting a distributed filesystem called “institutional memory” than slowly getting drip-fed context over 6 months.

I've been saying for a while that apprenticeship is the path forward for junior engineers in this new landscape, but, holy smokes, @tobi has taken it to a new level at Shopify. I love love love this.

Grocery is a $1.5T domestic market — bigger than restaurants, bigger than hotels. But it's running on technology from the Reagan administration. We just raised a $22M Series B for @VoriHQ to make every supermarket in America autonomous.

OpenClaw is the fastest-growing open source project, but there are no stories of running it safely in production at scale. As we started deploying agents internally at @brexHQ, we couldn’t stop thinking about this question. Agents work, but nobody wants to give them real credentials. Instead of waiting for a solution to emerge, we decided to try a novel approach: using LLMs to judge the network traffic of an AI agent. Today we’re announcing CrabTrap, an open-source proxy that intercepts every outbound request and blocks risky activity using LLMs, before it ever hits an external API. The results are promising; we believe it’s a meaningful step forward in the security of agent harnesses in production environments. Try it out today. (As a side note, it was really fun to work personally on a real systems problem again. And btw, if you want to work at a place where the CEO is building proxies at night, we’re hiring!)

Woohoo! Absolutely killer update from the @warpdotdev team. LFG 👏

The more enterprises I talk to about AI agent transformation, the more it’s clear that there is going to be a new type of role in most enterprises going forward. The job is to be the agent deployer and manager in teams. Here’s the rough JD: This person will need to figure out what are the highest leverage set of workflows on a team are (either existing or new ones) where agents can actually drive significantly more value for the team and company. In general, it’s going to be in areas where if you threw compute (in the form of agents) at a task you could either execute it 100X faster or do it 100X more times than before. Examples would be processing orders of magnitude more leads to hand them off to reps with extra customer signal, automating a contracting review and intake process, streamlining a client onboarding process to reduce as many straps as possible, setting up knowledge bases than the whole company taps into, and so on. This person’s job is to figure out what the future state workflow needs to look like to drive this new form of automation, and how to connect up the various existing or new systems in such a way that this can be fulfilled. The gnarly part of the work is mapping structured and unstructured data flows, figuring out the ideal workflow, getting the agent the context it needs to do the work properly, figuring out where the human interfaces with the agent and at what steps, manages evals and reviews after any major model or data change, and runs and manages the agents on an ongoing basis tracking KPIs, and so on. The person must be good at mapping the process and understanding where the value could be unlocked and be relatively technical, and has full autonomy to connect up business systems and drive automation. This means they’re comfortable with skills, MCP, CLIs, and so on, and the company believes it’s safe for them to do so. But also great operationally and at business. It may be an existing person repositioned, or a totally net new person in the company. There will likely need to be one or more of these people on every team, so it’s not a centralized role per se. It may rile up into IT or an AI team, or live in the function and just have checkpoints with a central function. This would also be a fantastic job for next gen hires who are leaning into AI, and are technical, to be able to go into. And for anyone concerned about engineers in the future, this will be an obvious area for these skills as well.

Another 🙌 for the @cloudflare workers platform: the CF API and the API MCP on top of it. Today: "duplicate this long WAF rule across all my zones". Done in seconds. 🎉

"Radical humility and endless paranoia are the only product strategies that make sense right now" What a fricking quote.

The big gap I see: context is not direction. A world model that reveals and routes information in real time solves a genuinely hard problem, but it leaves some others wide open: prioritization in a fog of ambiguity, accountability without hierarchy, and knowing where the model ends and human judgment begins. (Said differently: who decides, who's accountable, and how do you earn the credibility to be that person when there's no title doing it for you?) Excited to see how this evolves (and try it myself!).

There is no better guide than Claire. Snap snap.

Man, a lot of competitive harnesses are gonna get a lot better today.

Claude code source code has been leaked via a map file in their npm registry! Code: pub-aea8527898604c1bbb12468b…

I’ve found myself explaining LLMs to more and more friends and family. One component I’ve been covering a lot lately is model weights. If you aren’t totally clear on what these are, here’s a simple(ish) overview - no calculus knowledge required. A “what the heck are model weights” 🧵

Is Claude Code /remote-control Super flaky for anyone else? Got several CC sessions running (all start w RC enabled) on a caffeinated box at home, but on my phone, not all sessions appear, the ones that do show as idle, and trying to send messages is just met with a spinner.

WOW. Quite probably the best interview I've ever watched. Long, yes, but holy smokes, it's SO chock full of gold nuggets. Thanks to both of you.

Respect this and the Every team's thinking, but I'd flip the order: architect first, pirate second. Set the constraints (routes, API boundaries, repo separation, lib/component usage), THEN vibe code inside them. Speed without slop. The architect shouldn't be the cleanup crew. The architect sets the bones: the boundaries, the patterns, the foundation. Not a full blueprint for every feature; just enough structure to ensure that the pirates/builders are coloring inside the lines. I like to assume builders have architectural competency, but honestly that might be the hardest thing to hire for, and maybe why you're advocating for a separate role. For founders, you have to be both. As teams grow, I could see it becoming a real specialization.

Today I’m excited to finally share something we’ve been working very hard on behind-the-scenes, that we’re now sharing with the public, along with our launch partner. And this could quite possibly be the most challenging, and exciting thing I’ve done in my career - it’s a big day. As someone that has been building AI agents for years, I saw a gap in the market, and some real challenges that generalized protocols like MCP had with things like token-efficiency and security. When Google announced UCP, I knew it was going to be big, and the surface for online shopping would begin to shift. But with this shift, things like performance and security are everything. Generalized protocols made too many tradeoffs that I saw in benchmarking caused things like tool misfires, token boat, and some pretty scary stuff on the security side. I see this as a turning point in history, and for us, as a company that has been providing a leading AI fit platform for 14 years, the opportunity to really make an impact as this shift happens. So I am incredibly proud and excited to say that today we are announcing Agentic Sizing Protocol, a new AI-native protocol, designed for AI-agents in the conversion-critical hot path where every second matters and Enterprise-grade security isn’t a nice-to-have, it’s a must. I am also incredibly humbled and honored to announce our launch-partner, GAP, one of the most iconic brands in history, and a true pioneer and leader when it comes to adopting AI early. GAP is getting a massive head-start on AI shopping, and will be giving their customers a truly differentiated sizing experience powered by Agentic Sizing Protocol. Today feels surreal, so much work has gone into this, I couldn’t be more excited to pioneer this new protocol, alongside such an incredible partner - here’s to our agentic journey ahead! You can read more in GAP’s newsroom, link in the first comment below.