This is a raw stream of working notes. Some may be wrong, and mostly these will have little context, but I believe sharing raw thoughts is valuable in a way that polished blog posts are not.
"Nobody gets fired for buying IBM" used to mean: pick the vendor nobody will question. It was a decision driven by fear, not conviction. I think Anthropic is becoming the equivalent for AI, but for a better reason. At Pactum, we didn't choose Anthropic through structured evaluation. We started with Gemini because we're on
I've seen people try Claude or ChatGPT, get mediocre answers, and conclude AI is overhyped. But the power of agents doing real work for every employee comes from the agent knowing your company, your team, your processes. If you use the vanilla version and expect it to be mind-blowing, you're testing the wrong thing. Exceptional
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. They share a thread: the agent isn't replacing someone's work, it's gathering context I wouldn't have gathered on my own, so I can think
While we're in this mode of rapidly developing agent capabilities, I want to do my part in diffusing knowledge of what agents can do. Since Claude Code IS the software, I am using it more and more for everyday office work, and rapidly discovering new things that agents can (or cannot) do. My daily driver with those is
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? 2. Is it against the laws of physics? It's rarely either, at least in my line of work. Putting a problem in these terms makes that clear, which is encouraging.
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 bothered to figure out the clunky UIs and directory trees and subtle variants of tables. This is now automated for me. It's built for Claude Code, but it works with
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's been clear for a while now that the cost of creating software has come down radically, so software becomes disposable: more like a paper towel than a CNC machine. It hasn&
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 "Less, but better." * Strunk & White tell you to "Omit needless words." In fact, the paper People systematically overlook subtractive changes explores this concept. From the abstract: Improving objects,
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 API connectors etc). But it seems that Claude Code and Codex are strong enough general-purpose agents that you can just outsource (1) to one of those generic ones, and focus just
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 Youtube or your favourite podcast app. Excerpts: I’m not very surprised or disappointed by GPT-5, and that’s because the trajectory is actually quite straightforward. The scaling laws tell us
