AI increases labour supply rather than reduces it, and watch out for those second order effects on society at large:
Occupations more exposed to generative AI saw a rise in work hours immediately following the release of ChatGPT. Compared to workers less exposed to generative AI (such as tire builders, wellhead pumpers, and surgical assistants) those in high-exposure occupations (including computer systems analysts, credit counsellors, and logisticians) worked roughly 3.15 hours more per week …
... [... 425 words]Great post from Tina He on the future of work in the era of AI. Firstly, we’ve been coming at things all wrong:
Traditional economics might predict that AI-boosted productivity would reduce working hours, a four-day weekend for tasks that once took five days. But reality has different plans. We’re witnessing what I call the “labor rebound effect”—productivity doesn’t eliminate work; it transforms it, multiplies it, elevates its complexity. The time saved becomes …
... [... 315 words]Similar to the Model is the Product a couple of weeks ago, the bitter lesson here is that brute forcing problems with compute wins versus clever solutions. Scaling compute at inference time with RL is the latest application of the bitter lesson, and we’re already seeing it move the needle in production use cases (customer support and soon, coding). This has big ramifications in the AI application layer:
While many companies are focused on building wrappers around generic models, …
... [... 177 words]Let’s join the dots between a few different themes this week.
First up, cursor rule files are vulnerable to prompt injection attacks. It’s possible to embed prompts within the rules files and hide them using invisible characters.
You can then use this poisoned rule file to redirect cursor/your agentic IDE of choice towards malicious implementations. This is not a huge surprise - the point of rules files is to direct the LLM towards specific implementations. What’s changed …
... [... 501 words]I think this is a strong take on the on the consequences of the recent RL breakthroughs from Alexander Doria:
I think it’s time to call it: the model is the product.
All current factors in research and market development push in this direction.
Generalist scaling is stalling. This was the whole message behind the release of GPT-4.5: capacities are growing linearly while compute cost are on a geometric curve. Even with all the efficiency gains in training and infrastructure of the past two …
... [... 536 words]Lots to digest here. A few pull quotes from the press release. Coding use cases are the focus of the upgraded model:
Claude 3.7 Sonnet shows particularly strong improvements in coding and front-end web development. Along with the model, we’re also introducing a command line tool for agentic coding, Claude Code. Claude Code is available as a limited research preview, and enables developers to delegate substantial engineering tasks to Claude directly from their terminal.
It’s a drop in …
... [... 267 words]Hot take. Product teams talking too much about ICPs is a red flag. ICPs are for sales and marketing teams. They’re at the blunt end and need to narrow their focus to maximise win rate and build a hyper efficient growth engine.
Product teams need to know and understand their ICP to support prioritisation, but they should be thinking in terms of Product Market Fit strength across segments. We need to have that peripheral vision and understand the whole picture. This is how you expand PMF and …
... [... 91 words]I thought this post was interesting, not so much for conclusion about Grok 3 but instead for the range of tests that Andrej performs to get a feel for the capabilities of the model in <=~2 hours. It’s all there - the recall/reasoning without search of the GPT-2 training FLOPs, a few varied dev tasks, research tasks, search tasks (including a gut feel for hallucinations), ethics, personality, then a battery of standard LLM assessments (‘r’s in strawberry, 9.11 > 9.9, …
... [... 160 words]Another day, another AI dev flow. There’s some common patterns emerging now (use of markdown files like spec.md, todo.md etc.) and I thought the blog gave a nice step by step guide and prompts to borrow. Basically the advice reduces to “spend a lot of time planning with reasoning models up front”. I liked this thought too:
I have spent years coding by myself, years coding as a pair, and years coding in a team. It is always better with people. These workflows are not easy to …
... [... 140 words]Great post from Nelson Elhage (Anthropic pre-training team) on adventures coding with Sonnet. Much of the post just describes the same journey that a lot of us are on at the moment (I’m still finding these posts fun to read, I wonder when the sense of wonder will be replaced by one of fatigue?), but there’s a couple of thoughtful nuggets towards the end that I’ve pulled out here:
You can now generate thousands of lines of code at a price of mere cents; but no human will …
... [... 240 words]The title is a little click-baity, but the analysis of the paper in the blog is great. A fast download of one (quite hacky, fun) approach to getting scalable test-time compute.
The insights here are not novel, but Dario provides a strong mental model of how the AI system will keep evolving over time:
Shifting the curve. The field is constantly coming up with ideas, large and small, that make things more effective or efficient: it could be an improvement to the architecture of the model (a tweak to the basic Transformer architecture that all of today’s models use) or simply a way of running the model more efficiently on the underlying hardware. New generations of …
... [... 355 words]Here they come, Rocketable is a YCW25 batch startup following the AI Rollup model (see previous post). The plan here is to purchase profitable SaaS companies throwing off cash and use that cash to bootstrap more purchases, Omaha style. The investment thesis is the application of AI/agents allows full automation of any work done by humans within these small SaaS co’s (as it’s likely to be generic one assumes).
Feels like a tricky one, the exact businesses willing to sell in this niche …
... [... 175 words]There’s a few pieces on AI Rollups floating around and I think it’s worth getting familiar with the model as it looks like a trend.
The tl;dr is that if you build a vertical SaaS product you can grab more return not by making pure software sales, but instead by buying businesses and then leading the transformation of applying the software to that business; this is known as the growth buyout. The oft-cited example of the model is Metropolis, who worked out number plate recognition for …
... [... 249 words]Good list, I’ve read a few of these but lots more to work through. The framing here is useful; though the list of what to read shifts pretty much every week, I think it’s a good guide to the areas to sample from. I would add What are embeddings, Yi Model Series and Yann Lecun’s talk on Objective Driven AI.
... [... 60 words]I’ve long thought consistency is king - I think this applies in codebases of all sizes, not just those in the single digit millions as Sean describes. Here’s the summary, though the full article is worth a read:
Large codebases are worth working in because they usually pay your salary
By far the most important thing is consistency
Never start a feature without first researching prior art in the codebase
If you don’t follow existing patterns, you better have a very good reason for it …
... [... 133 words]DeepSeek-v3 dropped on Christmas day (!) a gigantic mixture of experts type model (671b total parameters) which sets a new SOTA performance for open source. Why should I care? What does this even mean? Well, the big news here is the training efficiency.
Firstly the total training cost was ~$5.5m (2.78m GPU hours). Now, this is the GPU cost of the training run only, not a total load (i.e. stuff like R&D and staffing costs are not included) but that’s a big gain. By way of comparison, …
... [... 198 words]Everywhere seems to be full of hype around o3 since Friday’s annoucement from OpenAI so I thought I’d summarise a few points I’ve seen shared in various places but not yet gathered in one place. We’re going to zoom in mostly on the ARC-AGI results, as I think that is the most interesting part. Before we do that, let’s introduce the ARC challenge.
ARC (Abstract Reasoning Corpus) was designed/created by François Chovllet, Author of both Deep Learning with Python and …
... [... 1040 words]Webdev Arena builds on the Chatbot Arena concept but provides a coding-specific benchmark that offers an extremely fast and cheap way for you to evaluate the vibes of the different models out there.
Given a prompt and two anonymised LLMs the arena builds two output React/Typescript/Tailwind apps side by side for you to evaluate - serving them up in an e2b standbox.
I suspect that as the frontier keeps moving it’s worth refining the prompt you use to test models (spend a bit of time making …
... [... 143 words]Some interesting ideas from Will on using generative AI to either manage the set of UI components shown to the user or generating the UI in raw pixels on the fly as we’re starting to see in gaming (i.e. Genie 2). I think a pixel based approach would be very complicated to do reliably, but an approach where a model dynamically generated the UI from a set of pre-defined components would be very interesting. Worth a read and a ponder about where we’re headed:
In place of a single …
... [... 156 words]