My agent use cases, part 2
In part 1 I covered the straightforward agent use cases: copyediting, onboarding, expense reports, Jira management. Those are about doing existing tasks faster. The
1 Mar 2026 · 4 min readCTO building AI products, CIO running enterprise technology. Working notes from both sides. About →
Essays and notes that best show how I think.
In part 1 I covered the straightforward agent use cases: copyediting, onboarding, expense reports, Jira management. Those are about doing existing tasks faster. The
1 Mar 2026 · 4 min readIn 2024, humans created software. In 2025, Claude Code (and Codex, and Cursor, and all the others) created software. In 2026, Claude Code is
10 Jan 2026 · 1 min readHere's a model I use to think about how AI will change work. Some parts of every activity will cost 1,000x
4 Aug 2025 · 2 min readShorter ideas, quick updates, and experiments in progress.
In part 1 I covered the straightforward agent use cases: copyediting, onboarding, expense reports, Jira management. Those are about doing existing tasks faster. The five below are different.
People sometimes use the word "impossible" too lightly. When I consider whether something is possible, I consider two angles first: 1. Is it logically provably impossible?
Today I published my first agent skill: using Statistics Estonia databases. Often I have some simple question and I know data exists, but I can't be
In 2024, humans created software. In 2025, Claude Code (and Codex, and Cursor, and all the others) created software. In 2026, Claude Code is the software. It'
When solving a problem with an existing system, most people tend to add. But often, removing makes a design better. * Dieter Rams's famous principle is "
I used to think shipping an agent product meant building: 1. The core LLM loop. 2. Skills: describing to the LLM how to do particular things (including building
Mostly talking about AI, Pactum and selling to enterprises. It was recorded at the end of August, so some things are already likely stale! Find the podcast on
I recently noticed that it's a bit clunky to talk about "users" of our agents. Building complex enterprise software, we have multiple types of
When things are stable, you make plans by anchoring to the question "what will change?". With your customers, your company, technology, regulation or anything else about
I have a 14,000-word document I maintain manually, to add into ChatGPT queries I make related to my role as CTO. It covers a lot of ground