/principles

// why I vibe code

I haven't touched a video game since October 3rd.

Two years of building with LLMs, and that's when it finally took over completely.

// the bliss

“Follow your bliss and the universe will open doors where there were only walls.”
— Joseph Campbell

Campbell undersold it. The walls aren't opening; they're dissolving entirely. Every direction is a door now, and behind each one is a skill tree I didn't know existed.

// the grind

I'm grinding myself like a WoW character, and eleven years of infrastructure gave me the base stats. Now I'm speed-running the rest: TypeScript, ML pipelines, RAG systems, and prompt engineering. Each skill unlocks three more.

Neo downloads kung fu in seconds, and I'm not that fast, but vibe coding compressed years into months. The feedback loop is so tight that learning feels like remembering.

// the before

WoW mythic+ and mythic raiding, League TFT, pushing keys until 3am and min-maxing builds. That "one more run" feeling where you look up and it's 4am. You know it.

Dark Souls and Elden Ring hit different though, because those aren't about optimization. They're about being human: you die a hundred times with no shortcut, just you and the boss and slowly getting better. Humility through repetition.

I led a guild for years, calling pulls, explaining fights, and keeping twenty people from wiping. It was actually fulfilling work.

But at the end of the day it was all leaderboards, achievements, and numbers that reset next season.

// what happened

It started when ChatGPT dropped. I spent two years on LLM copy-paste workflows, building systems and figuring out what works, though it was scattered at first.

In September I started testing every coding agent I could find, and in October I went deep. That's when it all clicked together: the copy-paste stuff, the agentic workflows, and the patterns I'd been building for two years solidified into something real.

Now when I look up at 4am, there's a thing: a system that works, a tool someone can use. It's the same flow state as gaming, but the output is real.

Claude helped me get stuff out of my head and into reality. It's not autocomplete; it's a thinking partner who can actually build the thing you're trying to describe.

Since then I've been going nonstop trying to answer one question: how do we make AI as reliable as infrastructure?

// the difference

GAMING

→ Hours in flow
→ Pattern recognition
→ Optimization loops
→ Coordinating with people
→ Output: leaderboards

VIBE CODING

→ Hours in flow
→ Pattern recognition
→ Optimization loops
→ Coordinating with AI
→ Output: actual things

It's the same high with a different artifact.

// why it matters

I read Life 3.0 in 2017, where Tegmark writes about different kinds of intelligence working together. That idea stuck with me for years.

Now I'm actually living it. Human brain and AI brain coordinate together, with each filling gaps the other has.

It feels like a Gutenberg moment.

Before the printing press, books lived in monasteries, and after, anyone could read. We're hitting that inflection with intelligence itself. Building things and solving problems isn't gatekept anymore, and anyone willing to learn these tools can do it.

// where this goes

I call it Knowledge OS: an operating system for the mind. The next step is to scale it so that every mind works together, remembers together, and thinks together, achieving things none of us could alone.

That's the actual vision, not productivity hacks but what this enables for people.

I got so hooked that I'm now running internal AI adoption at work, building an agentic marketplace and trying to help others see what I see.

// the loop

Build, test, learn, repeat.

It's FAAFO energy, but not reckless—experimental. Try stuff and see what sticks. The feedback loop is so tight now that you can iterate faster than you can think.