Breaking it on purpose
How do you find the ways an AI product fails before your users do?
Large language models become a mass-market product overnight.
source (opens in a new tab)Claude launched the same day.
Fed into: EXP-000 Ambient care-plan scribe
source (opens in a new tab)GPT-4 Turbo reads about 300 pages at once, and structured output becomes practical.
source (opens in a new tab)OpenAI's o1 thinks before answering: big gains on maths and code.
source (opens in a new tab)Claude operates a screen, keyboard and mouse: AI starts acting, not just answering.
source (opens in a new tab)An open standard for connecting AI to tools and data.
source (opens in a new tab)Claude Code previews: an agent that works in your codebase, not just suggests lines.
Fed into: EXP-005 Fold, EXP-006 Fold's review panel, EXP-007 This lab, rebuilt
source (opens in a new tab)NHS England publishes guidance on AI-enabled ambient scribing products in health and care.
source (opens in a new tab)Google's "Nano Banana" focuses on consistent characters and precise edits.
Fed into: EXP-005 Fold, A recipe for honest pictures: how to avoid AI image slop without copyright trouble
source (opens in a new tab)Anthropic gives Claude Mythos Preview only to cyber defenders, through Project Glasswing.
source (opens in a new tab)Claude Fable 5 becomes available to everyone, and Claude Mythos 5 to Glasswing partners only.
source (opens in a new tab)Google also releases its new frontier model to cyber defenders first, as Anthropic did with Mythos.
source (opens in a new tab)My personal context folders for Claude, which carry my projects and preferences across tools.
Fold's review panel, then agent teams and reviewers on later builds.
Before care had scribes: drafting care plans with AI in 2022
Read the logDeciding not to build: when no-code is the right call, and when it stops being one
Read the logThe bottleneck moved: where the time goes when an AI agent writes the code
Read the logNever mark your own homework: independent AI reviewers for a solo builder
Read the logNothing goes live unread: building a public site with AI agents, without losing control
Read the logThe best page, the worse journey: when an AI tool's quality isn't worth the effort
Read the logFrom wiring services together in Zapier to a back end written in code.
See the stackFrom a chat that wrote the instructions I pasted into the editor, to a planning session that writes specs into the repository for the builder.
See the stackFrom asking the same chat to a separate research tool.
See the stackFrom an editor whose AI wrote most of the code but which I had to stop from running scripts, to an agent trusted to build, run and test in its own session.
See the stackFrom one evaluation system I couldn't keep running, to small reviewers that each check one thing.
See the stackFrom a spreadsheet-style database to hosted databases and private repositories.
See the stackFrom layouts I had to fix for phones after launch, to a design tool and layout tests at phone and iPad sizes.
See the stackSign-ups go straight into the newsletter tool, with no automation in between.
See the stackFrom one model for everything to a different model for each job.
See the stackFrom a site I had less control over to one I own, edited in a content manager.
See the stackHow do you find the ways an AI product fails before your users do?
What does “good” mean for output nobody can mark right or wrong?
When AI checks AI, what checks the checker?
Where do a builder's time and judgement go when agents do the typing?
What should an AI know and be able to reach, and who decides?
When is a cheaper model the better product decision?
How do you design AI that people trust exactly as much as they should?
When building is this cheap, how do you decide what's worth building?
How this page is made
Built automatically from each build's start date, each learning note, skill, certification and guide version, the dates of the tools I switched to, the events in "What AI changed for me" and the AI milestones. Adding an item updates the timeline the next time the site is published.