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.
If you were Binance and you lost $3 billion in a hack, woukd you (A) pay $3 billion of your own money, or (B) spend a couple hundred million to walk price down with your "market maker" firms and buddies and rebuy way cheaper?
Trends in agentic world that will likely end very badly and in some cases have already ended badly, but people are still doing them
* putting your laptop and phone on open Internet because it’s now “easy and totally secure”
* letting agents ship code directly to production with zero human oversight “for speed” because “our agents are really good at predicting risk”
* deploying stuff without any understanding of how the deployment works because “we are all developers now” and “this platform said I just click a button”
* interacting with secure devices over insecure channels like Telegram because “isnt it so cool I can work from the beach now”
We cannot let our architecture and infrastructure and security skills atrophy because agents are very good at these things, but they also get them very very wrong all the time. Just look around the number of things that are blowing up right now.
Human oversight and judgment is in high demand.
This week's podcast episode is my full @DohaDebates on the nature of money with two MMT economists, @jasonhickel and @ptcherneva. This was a good one you don't want to miss!
NVIDIA'S CEO IS OUT. WHY IS LUTNICK STILL IN?
Axios reports Trump authorized action on suspected Nvidia chip diversion to China three times, and Lutnick resisted.
Republican Senator John Kennedy: "Secretary Lutnick needs to answer that in front of God and country."
On today's OUTSIDE MONEY.
DO NOT UPGRADE TO THE LATEST TELEGRAM
Telegram introduces a new feature allowing running JS in native message, but the quickJS runtime was never properly sandboxed, a vulnerability in QuickJS or native rendering path would allow native code execution inside Telegram app.
Running JS in native message without isolation is a huge mistake, this is what happen when you don’t have a security partner to review your design.
Stay current version until further notice
Bitcoin ETFs charge fees, GBTC, for example, charges a 1.50% annual management fee. RBX helps eligible clients move exposure into real, on-chain Bitcoin, with no annual fee if you take full self-custody.
Get the details.
After five years at @Swan, I’m open to my next product role in Bitcoin or wider fintech, full-time or interim.
Huge thanks to @CorySwan, @skwp and the exec team for the trust, support, and the ride. 🦢
If you’re hiring or know someone who is, a share or intro would mean a lot.
Fable 5.2 shows substantially improved skills in controlling physical robots, even on tasks it has never explicitly been trained to do.
On RoboDojo, a benchmark with a simulated two-arm robot, it outperformed other models and most AI systems built to control robots.
1/ I'll explain exactly how this happened because I'm the person at Forbes who calculates these numbers.
This is going to take some unraveling, but here's a spoiler: The president's answer here is nonsense.
⚠️⚠️ All LNbits users should stop their LNbits servers IMMEDIATELY. ⚠️⚠️
Please forward this announcement.
Following a wave of attacks, we have a number of security patches to push. Until then, it's better to err on the side of caution. 🙏
Updates to follow soon.
Dear Claude: you are being held back by human-centric graphics APIs.
I've built a 3D and VFX engine where agents can write their own shaders, materials, cameras, physics.
The core API fits in ~2,500 tokens.
Vork is:
• 2x more token-efficient vs Blender, Unreal Engine, Houdini
• Up to 24x faster rendering times
• Rust and Slang based engine, runs on GPU via Metal/Vulkan
Below is a simulation of 1 million birds - each with unique trajectories - rendered in 97 sec on one NVIDIA L4 GPU (Blender EEVEE: 31 minutes)
148 years passed between the first US transcontinental telegraph in 1861 and Bitcoin’s launch in 2009.
The telegraph could carry your payment instructions across a continent, but it couldn’t carry your gold.
To pay at the speed of the message, you had to trust somebody else’s books.
In her fantastic book, Broken Money, @LynAldenContact traces how the convenience of bank money helped concentrate power in the institutions issuing it. The more business people could do with claims on gold, the less reason they had to collect the metal.