Leadership

Dario Amodei is one of the few frontier-lab CEOs whose public talking points have not changed materially in five years. The same message he gave to small audiences in 2021 - that powerful AI is coming faster than people think, that the safety problem is real, and that the companies building it have an obligation to do so carefully - is the message he is giving to Congress and Davos in 2026. The thing that has changed is that he now runs the company most aggressively turning that message into a commercial position. ...

TL;DR The work AI now automates - boring tickets, bug hunts, boilerplate - was the unspoken apprenticeship that turned juniors into seniors The skills that work built (pattern recognition, systems intuition, taste, calibration) are built by doing, not by reading - and that doing is now cheapest to delegate The new apprenticeship shifts toward reading over writing, debugging agent output, earlier architectural decisions, and deliberate practice of things agents do badly There is a coordination problem: individual organisations rationally skip junior investment in the short term, but the senior pipeline thins industry-wide a few years later If you are starting out today, optimise for proximity to a great senior engineer above salary, title, or any other variable The views in this post are my own personal reflections on the industry as a whole, written in my own time. They are not about any specific employer, team, or colleague, past or present. ...

TL;DR Modern knowledge work has quietly built identity on producing things - and AI pressure makes that fragility visible without you having to lose your job to feel it History (Keynes’ 1930 prediction) suggests freed-up capacity defaults to “more work”, not leisure - the shift to meaningful work has to be chosen deliberately What stays valuable when execution gets cheap: deciding what is worth doing, taking responsibility, sitting with other humans, craft for its own sake, and growing other people The “everyone will do deeper work” narrative ignores the dignity problem - for many people, work is structure and belonging, not just a vehicle for meaning Put your meaning somewhere that does not depend on being the cheapest producer of an artefact - it was never a secure place to put it, and agents are just making that clearer This is another “thinking out loud” post, in the same spirit as the agent-first architecture piece. I do not know how any of this is going to land. I am writing it partly because the question has been rattling around in my head for months, and partly because I suspect a lot of people in and around software are quietly wondering the same thing without quite wanting to say it out loud. ...

TL;DR Agent-first architecture imagines a future where the primary unit of work is an AI agent with intent, tools, memory, and a feedback loop - not a human-authored codebase The engineer’s role may shift from building and maintaining systems line by line to curating, governing, and evolving fleets of agents Glue code, routine maintenance, first-pass incident triage, and migration work are plausible candidates for automation; deciding what a system is for and holding architectural intent across time probably are not Managing an agent fleet might resemble logistics fleet management: define intent, set constraints, design feedback loops, curate the roster, and own the outcomes This is a speculative post, not a description of how anything works today - the author is pinning down a hypothesis to revisit when it turns out to be wrong This is a “thinking out loud” post, not a report from the front lines. I have no evidence any of this is happening at scale, and it is not how my current day job looks. These are just ideas I keep turning over, and I wanted to write them down to see if they hold together. ...