
I will be teaching my two-day course, Practical Messaging, at NDC Oslo this year. I suspect it will be the only public presentation this year. ndcoslo.com/workshops/practi…

Principal Engineer in London, speaker, tabletop gamer, geek. Tattooed, pierced, and bearded. The 'guv' on @BrighterCommand. Also @ICooper@hachyderm.io He/him.

I will be teaching my two-day course, Practical Messaging, at NDC Oslo this year. I suspect it will be the only public presentation this year. ndcoslo.com/workshops/practi…

i'm back on the job market again - golang - mid level role - location flexible ⏰ pls rt for help ⏰

If you can wait infinitely long, you can essentially run a full search of all possible combinations of components that satisfies a given query. You don't have such luxury in reality, there is a small time window in which you expect an answer.

I’ve had this conversation with a few people earlier in the year. Game theory suggests everyone shares, except you, is optimal, which means folks stop sharing. My value becomes what an agent doesn’t know because it’s not written down. Worrying.
The shelf life of thin software is collapsing. Value is rapidly concentrating in things that are genuinely hard to build or replace. And the knowledge required to build on those layers is becoming too valuable and it creates incentives not to share knowledge.


I saw demos of at least 10 "software factories" last week from various teams at Microsoft..

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.

Applications are now open for the Anthropic Residency, a paid, fixed-term research program for academics, technical founders, and staff-level engineers who want to make AI safe and beneficial for everyone. No ML background is required. Apply by November 22: alignment.anthropic.com/2026…

HOY NO VENGO A OFRECER MIS SERVICIOS. HOY VENGO A PEDIR UNA OPORTUNIDAD. Tengo 49 años, una esposa y dos hijas que dependen de mí. Desde abril de 2026 estoy desempleado y necesito trabajar. No es fácil escribir esto, pero hoy me toca pedir una mano. 🧵

At this point @andyburnham’s party has passed ill-advised Satanic Panic and into full scale censorship of the UK’s citizens. @LabDRN
These sites are set to be banned for under-16's in the UK. And when they mean banned for under-16's what they really mean is YOU will have to ID yourself to use them. Truly the ridiculous UK surveillance state is out of control. Kim Jong Un will be phoning for tips.

Whoa this looks great! What's the catch? netwasm.com/

Darker V5 is out. write.as/ian-cooper/darker Streaming queries ▎ • Polly V8 resilience ▎ • OpenTelemetry tracing ▎ • Validation + HybridCache caching ▎ • Agreement dispatch ▎ • Startup pipeline validation #dotnet github.com/BrighterCommand/D…

We need to express caution about AI detection tools. They may be nowhere near as accurate as the lynch mobs want to believe. theguardian.com/books/2026/n…

One question I ponder: would F# be a better #dotnet language for agents? I have previously had problems rolling out F# because developer knowledge was low. But agents might change that balance. Railway-oriented Programming comes from @ScottWlaschin in that community, for example.

.NET Developer Survey 2026 nam.dcv.ms/UPTcBN6NBa

Mostly, I think this is wrong. I started my career as an “analyst programmer” building PC solutions for teams using RAD tools like FoxPro. I expect to see many developers moving back into that role, in small software houses building bespoke solutions for SMEs.
In the next 3 years, I think we’re going to see huge cutbacks in engineering headcount and equally huge increases for customer-facing roles. LLMs can do most of the software engineering role and it’s going to keep increasing. There will be some left, but you have to legitimately be one of the best. Meanwhile, anyone who has a customer-facing role (product, sales, etc.) just immediately 10x’d their value for one simple reason: no one likes getting AI slop thrown at them. And because the supply of software is increasing, there will be more demand for these roles. If you’re in a customer-facing role, congratulations. You just got a golden ticket. If you’re a dev, you’d better be the best or start developing non-technical skills.