Thoughts after talking to lots of engineers in London in last couple of days:
• Everyone's moving into the same direction and getting more and more agent-pilled, but all on individual speed. No group of engineers right now is uniformly agent-pilled.
• Becoming agent-pilled is a one-way door. You only realize this once you've gone through. Many think they "get it" but haven't made the switch yet.
• Wild how many orgs are still treating agents as "thing that writes code on my computer" instead of robot-engineer that can help with whole SLDC.
• Teams are drowning in PRs and code review. No process has been changed yet, even though this is the biggest dev productivity lever of last 30 years, engs still work off tickets like nothing happened. Wild.
• Barely anyone realized yet that, hey, even if the model isn't good enough to write the code the way you'd write it [doubt it], they can surely write all of the peripheral tooling to speed you up.
• Very few engineers have imagination to come up with better tool. Instead of reviewing code in diffs, line by line, think: if I could wave a magic wand and make tooling disappear, what tooling would I want to gain confidence in this change being correct? Full instrumented/traced end-to-end runthrough? Demo videos? In-production probes? High-fidelity and anonymized production data fed through test runs? New testing environments with the greatest debugging MCP support one can imagine so agent can inspect everything?
It's time to dream big.
But seems like most people's dreams don't reach further than "this agent works off the tickets assigned to me 10x faster than I can."
Me: I pine for the bygone days of deep work and focus.
Also me: ship all the easy low-risk stuff because I love cheap thrills, as the pile of threads that require actual close attention and consideration grows and grows.
I just finished talks about my software factories at two conferences. Afterwards a bunch of people came up and told me what they were surprised about. Here is a distillation of what people thought were hot takes from my two talks.
First hot take: I tell everyone to slow down. Most speakers go on about how fast they're going, but I strongly believe in pacing AI outputs to human speeds. I regularly tell AI-pilled CIOs and CTOs to chill: almost nobody is _actually_ going fast with AI. Engineering still moves at engineering speeds, and business moves even slower. The ones pushing too hard are starting to see downtime for it.
If you don't pace your AI to human speeds, everything starts breaking around you, even at small operations like my online video game. I only have about a dozen humans working with my factory, and only a few hundred active old-timer players in the community who get along well, and still, introducing AI has still been very rocky.
My agents have, at times, overwhelmed my players with features, my accountant with emails, my merge queue with tickets, and my machines with load. Agents have pissed off my admins, resulting in name-calling, they've made messes in the game, and they've launched broken OSS without permission. The list goes on.
I can get away with all this chaos because everyone involved in my operation is very forgiving. They're excited by the potential. But even so, I had to learn to slow down, real fast. And so that's what I preach.
Hot take #2: Should you buy a software factory? Do you even need one? No. You probably don't need one. Factories take an extraordinary amount of upkeep. They turn into garbage mountains unless you put a frightening amount of time and tokens into curating them. I had to burn my previous five factories down since it eventually became cheaper to rewrite them than to fix them. So I'm not out there advocating for software factories or swarms just yet. If you do want one, be aware that it is a significant commitment of both money and human leadership to keep one running.
Several people told me that I was the only one who stood up onstage, at either conference, and said Build, don't Buy. But my experience is that software factories grow to be highly bespoke to your domain. Mine is super tangled up with my game, and I think that's inevitable. Because the factory is not just building my product, it's supporting it too. It's a company in a box. And they're easy for Claude to build for you.
Third and arguably hottest take: Next year will have a lot of human/agent and agent/agent office drama, resulting from bringing in AI employees, and it will be gloriously funny, but also frustrating.
Many of you are already on this bandwagon, but everyone next year will have a personal chief-of-staff agent. Busy people, even hobbyists, will have whole entourages of helper agents. The hot take is that people will become so dependent on these little private entourages, that they'll bring them to work. Your people will talk to my people, etc. Whole protocols will emerge for private entourages negotiating work between humans, inside companies big and small.
Nearly all humans will wind up having to start working with AI employees next year, and it'll be the beginning of the biggest cultural change we've seen in a hundred years.
So that's the hot takes. Slow down. Only build a factory if you think you really need one. And focus on empowering yourself with your own agentic chief of staff (or team). Your entourage will define how you work with others, so start by perfecting how you work with them yourself.
AI interfaces nowadays are still pretty much turn-based.
In my PhD thesis, I thought about what interaction would look like if we could go beyond taking turns.
One example is intra-turn interaction:
this is not a kpi people. its not a flex.
7000 PRs that you havent read adds no value, adds risk, and lacks intent
like what are you trying to prove? that you dont care about your software?
There is no excuse anymore. You can’t hide behind SOC2.
Running continuous red teaming against your company is now:
A. Economical
B. Absolutely critical
Red teaming is just truth seeking about the state of your security from first principles.
SOC 2 is reasoning by analogy that you should be secure.
If there is one thing the AI revolution has taught me, it’s that 99% of people cannot extrapolate. At all. Quite literally people cannot imagine or visualize progress or changes beyond the current state. Complete inability to predict the future.
the most import skill in 2026 is still being able to tell your agents "wtf is this crap, no, not like this"
if you stop doing that, you're basically fucked, despite what some devfluencers would like you to think.
You don't need a software factory. You need an abstract software factory provider which can instantiate concrete software factories without coupling the client to a specific software factory implementation. Have some fucking self-respect.
@ryanflorence Amp does most of this except the chat bit but I’ve seen screenshots of new stuff coming 🫣 it’s my favorite tool I’ve used in years, I have become a fanatic.
@a16z State of Longevity report is out!
@evajsteinman and I surveyed 500 Americans to predict what's next.
We're also interviewing people at the cutting edge of health & tech about what they do themselves. My interview with @hubermanlab is out today. https://t.co/CApCjv8xv9
I may be able to help shed some light here.
While they all sound similar, I hear a lot of people use "passphrase", "passkey", and "password" interchangeably.
What makes it even more confusing is that you can store all three of those things in your password manager 🧵
We asked GPT-6 Astra to edit Qwen3.5-0.8B weights to improve math.
It directly changed only 0.016% of weights, fixing 0.8B's reasoning loops & improving math up to 6x and even instruction following 3x, without gradients or training.
We call this Weight-Space Programming: frontier LLMs can now natively read/write neural network weights! 🧵
Blog: https://t.co/bOWCcFhCVq