The Personal OS

I spent ten years at LEGO. Not designing sets – working with the material itself. Polymers. Injection moulding. The physics of how melted plastic flows into a mould and becomes something a kid picks up and never puts down.

You develop a feel for it. Not just the science – the craft. You learn that a 0.02mm difference in a mould wall changes how the part ejects. You learn to read a machine by its sound. After enough years, the tools become invisible. You stop thinking about the process and start thinking through it.

When I left LEGO and started a 3D printing company, people said it was a big leap. It didn't feel like one. Same logic – material goes in, object comes out. The loop just got shorter. Instead of months from design to production part, it was hours. The machine sat on my desk instead of filling a factory hall.

Then I built an AI-powered children's book product. Custom stories, custom illustrations, printed and shipped. Another step removed from the physical. But the pattern was the same: understand the material, shape it, ship something real.

Now I spend my mornings in a terminal. Not writing code in the traditional sense – more like directing it. I describe what I want, an AI builds it, I shape the output, deploy it, and move on to the next thing. Last month I shipped six tools in three weeks. Not prototypes. Working products, live on the internet, doing useful things.

Here's what I keep thinking about.

Every tool I've ever used – the injection moulding machines, the 3D printers, the design software, the code editors – they were all generic. Built for everyone, configured for no one. You adapted yourself to the tool. Learned its interface, its quirks, its constraints. The tool didn't know you.

That's changing.

Right now, I have a workspace where an AI reads my context files at the start of every session. It knows what I'm building, what I've shipped, what's next. It runs commands I designed. It follows patterns I set. When I say "screen the feed," it knows what sources to check, what filters to apply, and where to put the output.

This isn't an app. It's not a SaaS product I'm subscribing to. It's closer to what I'd call a personal operating system – a layer between me and the digital world that's shaped around how I think and work.

And I think this is where everything is heading.

Not the metaverse. Not another platform. Something quieter and more fundamental: the interface itself becoming personal. Your tools knowing your context. Your workflows encoding your judgement. The gap between intention and execution collapsing – not because the AI is smarter, but because it's yours.

I think about the LEGO factory floor sometimes. Every operator had their station set up differently. Same machines, same moulds, but the experienced ones had arranged everything – the tools, the inspection lights, the reject bins – in a way that matched how they moved. Their workspace was an extension of how they thought.

We're about to have that digitally. Not a shared operating system that millions of people use the same way, but personal systems that evolve around individual people. Your AI doesn't just answer questions – it maintains your projects, remembers your preferences, runs your daily operations. It becomes the workshop, arranged around you.

The material changed – plastic, filament, pixels, prompts. The impulse didn't. You see something that doesn't exist yet, and you build it.

The difference now is that the building material is getting personal.

I'm going to write here occasionally. Not on a schedule. Not about a topic. Just thinking out loud about what it's like to build things in a time when the tools are changing faster than anyone can document.

If that sounds interesting, stick around.