Bad things happen when you are grounded in the real world.  Ergo, in systems architecture, we constantly look for feedback loops. Negative feedback loops provide stability (like a thermostat). Positive feedback loops provide amplification, but without a governor, they inevitably lead to system runaway and collapse.

You know the story of the Golem of Prague? The Rabbi builds a protector out of clay. It works great until it doesn’t. In engineering terms, the Golem failed because it lacked a governor—a negative feedback loop. In systems architecture, positive feedback loops without governors don’t just grow; they run away and tear themselves apart. That is exactly what it appears we are building with this circular financing of AI where capital flows from Big Tech balance sheets into startups and immediately flows back as revenue.

I’ve spent a lot of time, and acquired a lot of scar tissue, in this industry, and if there is one thing I’ve learned, it’s that most people are terrified of looking different. People hug the center of the road because it feels safe. But as Jim Hightower once said, 

“There’s nothing in the middle of the road but yellow stripes and dead armadillos.”

When we were building the early versions of PowerShell (back when it was Monad), we had a massive fight over a single word. It seemed trivial to everyone else, but I knew it was a hill worth dying on. It was the fight over the word Cmdlet.

The disagreement wasn’t a matter of wordsmithing; it was a foundational issue about establishing the cognitive contours of the product – how people would think, learn, find things, and form a community. It was an issue of soul.

I’ve been doing Office Hours and the topic of AI has been in almost every one of the conversations. Everyone is wondering what the right play is with AI. A number of people are concerned about it replacing them. I’ve been giving the following advice, “Treat AI as an awesome teammate”

I was telling someone recently that I studied Physics & Philosophy and that Philosophy taught me the art of asking great QUESTIONS, while Physics taught the art of creating great ANSWERS. So let’s start with a great question:  What is a Team?

We don’t build teams just to have more bodies in the room. We build teams because we are all flawed. Every single one of us has peaks of high capability and deep valleys of incompetence. The theory of a team is that it is a structure designed to amplify our strengths and compensate for our weaknesses. Putting my SRE hat on, you can view it as an architectural pattern for resilience and error correction.

If you stop looking at AI as a threat and start looking at it as a teammate, the dynamic changes. You figure out how to use it to compensate for your weaknesses. As I’ve said many times, I am a deeply flawed human (that is why you can use wildcards everywhere in PowerShell) so I need awesome teammates to function.