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.
@mmilinkov Huge news!! Congratulations on making this decision and thank you for getting you've built at eclipse and throughout the open source ecosystem!! You are leaving enormous shoes to fill.
Mike you have done an amazing job with Eclipse and building this community. You inspired and mentored numerous Community Leaders, Executive Directors, Software Engineering Leads, and more in the Open Source world.
Congratulations on what you've built and in this next step!
I am publicly announcing today that I am starting the process of retiring as the Executive Director of the Eclipse Foundation sometime in mid-2027. So this is not goodbye yet. It's more like I am just starting to turn towards the exit sign....
Why now? I just recently turned 66 and I had two grandchildren born this year. It's time to spend more time with my family. Plus almost all of my golfing and fishing buddies are already retired!
This process is going to take some time. We're aiming for the middle of next year, but that is a flexible target. Neither I nor the Eclipse Foundation are in a particular rush, and it is important that this transition happen as smoothly as possible.
I can't believe that I have done the same job for 22 years! (23 by the time I'm done.) I have been truly blessed to have a role that has been so challenging and enjoyable for so long. There are so many people who have helped me along the way that I am not even going to try to list them. But a sincere thank you to all.
More details are in my blog post and FAQ:
https://t.co/JiBIpTRcXk
I see a lot of ways that Agentic commerce is being built, but simple computer use is perfectly situated for the current state of the world. All others imagine a perfect world - that we don't live in.
I'm currently a big fan of @Muse
@CommerceJohn@josephfcox Oh! Hi! This thing is still on.
It's a splashy headline, but it's not entirely accurate.
Claude is one of the many tools available and can be enabled for departments, projects, or individuals.
@frankout@Clear This happening more and more. Was at PHX earlier today and TSA-Pre moved significantly faster than clear. Clear was disorganized and the machines slow.
Next week, I'm traveling to Japan and Australia. My goal is to connect with the local #Drupal community in each country, discussing the future of Drupal, learning from each other, and collaborating. See https://t.co/afFVh5v1JZ. Hope to see some of you there!
@Bowl_of_Worcel Really great that this show left a lasting impression on you. The man behind that ROBOSHITHEAD t-shirt recently passed away and your story came up when pulling up old content he created. Thanks for sharing such a positive story!
Drupal Association former board chair @baddysonja will speak on the main stage at #WebSummitLisbon! Join her session to learn the story behind one of the biggest open-source projects in the world and how Drupal moved beyond the hype. Learn more: https://t.co/WzyoGtlgdF
🌟 One week after an incredible #DrupalConLille 2023, we want to extend our sincere thanks to all of YOU! 🙌🏼 Your enthusiasm and participation made it unforgettable. Can't wait for DrupalCon Europe 2024 in Barcelona – it's going to be epic! 🌍#DrupalConBarcelona2024@KT_Congress
🌟 One week after an incredible #DrupalConLille 2023, we want to extend our sincere thanks to all of YOU! 🙌🏼 Your enthusiasm and participation made it unforgettable. Can't wait for DrupalCon Europe 2024 in Barcelona – it's going to be epic! 🌍#DrupalConBarcelona2024@KT_Congress
@GergelyOrosz This could be blanket requests, but couldn't a reasonable policy be to respond with information that requires no verification, a request to verify identification and a data set that covers both rules?
@GergelyOrosz Honest question, why would it matter? The person, if verified, is requesting their information. If they left out the GDPR or CCPA details would it not be processed? Does company policy state that unless you are explicitly covered no data is provided?