Ai

Everyone’s either panicking that AI will replace them or assuming they don’t need to learn anything anymore. Both miss the point entirely. AI amplifies what you already know. If you understand distributed systems, you’ll use AI to build better ones. If you don’t, you’ll use AI to create distributed disasters. The difference? When that AI-generated code breaks in production — and it will — you need to know why. When it doesn’t scale — and it won’t — you need to understand the bottlenecks. When it creates race conditions, memory leaks, or architectural nightmares, GitHub Copilot won’t save you. Your fundamentals will. ...

The biggest news in tech this week (which isn’t over yet) is, without a doubt, that Cloudflare is about to introduce a pay-per-crawl model for AI bots—huge in many ways, as let’s not forget that approximately 20% of internet traffic is routed through Cloudflare. I have many thoughts right now, and it will take some time for them to settle. A good analysis and explanation of why this move is needed and is a good first step can be found in yesterday’s article by Dries Buytaert’s, The Web’s Broken Deal with AI Companies, which I recommend everyone read. ...

I’ve been doing “agentic coding” for some time, and well, it’s weird. On stable, mature technology (in my case, the C#/.NET stack), it is beneficial, as it significantly boosts productivity. But, there’s a bit, and that’s that I’m not programming anymore, or very little now, and I love coding. I love entering “the zone” and solving complex problems, one at a time. It’s always been my superpower. Will I still have fun in the future now that I can delegate most tasks to Claude Code? ...

Quoting straight from Jim Nielsen’s note on LLM training on copyrighted data: As a broke teenager, the web was this strange wonderland where you could access all kinds of copyrighted material using tools developed by fringe individuals/communities: Napster, Kazaa, Torrents, Usenet, etc. These tools (at least in the beginning) weren’t really made for profit, just to subvert the gatekeepers (and yeah, steal their profits). Now — in a strange twist of irony — things seem to have flipped: ...

In the 2030s, intelligence and energy—ideas, and the ability to make ideas happen—are going to become wildly abundant. These two have been the fundamental limiters on human progress for a long time; with abundant intelligence and energy (and good governance), we can theoretically have anything else. – Sam Altman

I’m just back from watching Mastering Claude Code in 30 Minutes, a talk by Boris Cherny, who, I learned, created Claude Code. I was struck by Boris’s reply to one question from the crowd: Hey, why did you build a CLI tool instead of an IDE? Yeah, it’s a good question. There are two reasons. We started this at Anthropic, where people use a broad range of IDEs. Some people use VS code. Other people use Zed, Xcode, Vim, or Emacs. And it was just hard to build something that works for everyone. And so the terminal is just the common denominator. The second thing is that at Anthropic, we see firsthand how quickly the model is improving. I think there’s a good chance that by the end of the year, people won’t use IDEs. And so, we want to prepare for this future and avoid over-investing in UI and other layers on top. Given the way the models are progressing, it may not be practical to work on them soon. ...

Despite what tech CEOs might say, large language models are not smart in any recognizably human sense of the word.

Since yesterday, Claude Code has been included in the Pro subscription we’re signed up for. I’d been wanting to try it for a while, and now nothing was stopping me. Only yesterday (a curious coincidence), I read AI Changes Everything by Armin Ronacher, which gave me a glimpse of the potential and made my hands itch to try it. The initialization of Claude on the repository surprised me; the analysis (reported in CLAUDE.md) is thorough and reveals a good understanding of the project, including both the code and the general functioning, strategies, techniques, technologies and libraries employed. ...

Today’s Armin Ronacher’s AI Changes Everything strongly resonates with me1. I may not be using Claude Code as a daily driver as he now does, but I’ve slowly and steadily introduced large language models (LLMs) into my routine, and I’m reaping the benefits. It wasn’t the purpose of his article, but I wish Armin had gone into the details of how, why, and when he delegates tasks to Claude Code. Update: Armin later a follow-up. ...

Run Your Own AI by Anthony Lewis is a concise tutorial on how to run large language models on your laptop from the command line via llm-mlx. It focuses on Macs M-series, but it’s also suitable for other hardware. Saving it here for a friend.