Last month, I typed a single prompt into an AI system and walked away. When I came back, it had read a client's use-case document in German, designed an evaluation plan, generated synthetic test data, created a project on our platform, run the experiments, analyzed the results, and assembled a polished seventeen-page presentation with concrete takeaways. No edits. No follow-up instructions. One prompt.
The week before, I built a detailed month-by-month financial model for our annual investor strategy meeting - multiple scenarios across ten spreadsheets, a twenty-page presentation covering our current business situation, strategy, and financial options - from a single description of what I needed. A year ago, that would have been days of focused work.
I keep cataloguing these moments. A complete demo application: working backend, functional frontend, integrations with external APIs - one-shotted from a prompt. A production feature implemented from my phone that would have taken our engineering team weeks. Our entire company knowledge base including onboarding docs, evaluation frameworks, deployment playbooks: embedded into agent workflows that chain together like dominoes. Tip one, and the whole sequence runs. Each time, the same thought: this was not possible just three months ago.
Four percent of all new public code committed to GitHub, the platform where most of the world's software is built, is now written by a single AI system: Claude Code. Analysts project that share will exceed twenty percent by year's end.[1]
Four percent sounds small.[2] Imagine four percent of all new buildings in your city, designed by a single architect who did not exist two years ago. An architect who works around the clock, who gets faster every month. You would pay attention.
I run an AI evaluation company in Germany; we help organizations assess and deploy AI systems in regulated contexts. Our work is to make AI use safe and reliable, but on the pace of progress itself, we are bystanders. Tracking capability is my job. I was watching closely. And I still did not fully see the speed of what was coming.
Many people working in AI have been trying to articulate what they are experiencing. Matt Shumer compared the current moment to the early days of Covid, a period when insiders could see the wave building but the rest of the world had not yet felt it.[3] The comparison is apt. When people ask how work is going, I default to the measured version: we are integrating AI tools, it speeds things up, a gradual shift. That is not what is happening. What is happening is that my productive output has multiplied in ways I would not have believed six months ago. I may be biased. I work in AI, and proximity shapes perception. But the people arriving at similar conclusions span industries and continents, and many of them have no stake in the technology's success.[4]
To understand how we got here, we need to look at a single week: the first week of February 2026.