wrong tool

So my original problem is this: I want campaigns that produce the kinds of moments we get, and to do that, I need to remember what happened and create beats that take time.

I had the misfortune recently of reading a lot about the Hugging Face disaster, and what struck me while reading it was how a lot of that it could have been avoided by security measures on the part of Hugging Face.

I want to talk today about a really radical innovation that Nutanix built that is very unique to our platform, and the side effect of a feature the team built.

The other day, I remarked that it was possible that Apple’s R&D budget for 2025 equaled the entire R&D budget for tech in 1980.

One of the things that has been bothering me when I look at AI is that the advantages of the current foundation model hinge on their use of the most expensive part of computing infrastructure, which is global memory with low latency.

I’ve talked a lot about the advantages of Nutanix’s architecture, and at some point I’ve appealed to reason, I’ve appealed to revenue, I’ve appealed to existence, but I haven’t really explained the nuts and bolts of why.

I reject the idea that humans have no role to play in the future of software development.

I wrote about the notion of survivability before – survivability requires portability.

I have been spending a lot of time on the next phase of system administration, agentic system administration.

I have come here to gloat and observe.

Notes from moving a D&D distillation off the API and onto two boxes I own.

Over the past few months, I have been working on a system I call “CampaignGenerator,” and one of the critical questions for that system is: how do you store state and make state retrieval fast?