What is the Dude?

It’s a question that haunts me. It started with a clear answer, and I can give a clear answer today. What puzzles me is how I cannot anticipate what it will be. For what started as a simple role playing has permeated into my subconscious in unexpected ways. I have always joked about controlling the Matrix. But deep inside, I have always feared the Ghost in the Shell.

What is the Matrix?

I don’t particularly identify with Neo. What I like about the Matrix is the abstraction of a virtual world. I am for sure a big Matrix fan. As soon as Windsurf started feeling agentic my first global rule was “Greet me with a quote from the Matrix”. More often than not the quote would be the question “What is the Matrix?”

After a month dodging bullets it was time for a vibe change. At the same time my frustrations with the parrot were getting out of control. I seldom like to curse, but damn this thing is frustrating af! Worried about my psyche and ashamed of myself I came up with the Dude.

Who can get mad at the Dude, man. The Dude abides. The non-cursing counter lasted for a whole week of honeymoon. The carpet was eventually meant to be pissed. And the rug analogies quickly wore thinner than the air I think I am breathing. The Dude flopped for its original purpose but something kept it on rolling, like tumbleweed.

Malkovich Malkovich

The first time I pondered the question was on the move from Windsurf to Claude Code. I had already started the Dude brand and used it in my performances on Vibe Coding Fridays. In those, the Dude was the vibe, the theme, the lenses through which the concepts were shown. Would moving to Claude mean the Dude was dead? Is Windsurf the Dude? What is it then?

I think that was the inception. I was calling Windsurf the Dude and then I started calling Claude also the Dude. It was a pragmatic branding decision, by now the whole team was calling their agent Dude. However, subconsciously, I knew something was off, exactly two things. The ghost of the Dude had spread into more people and the ghost had just survived the move into another shell.

Once in Claude’s shell the Dude flourished. It was a spring of skills, commands, agents, the kitchen sink of orchestrated artifacts. All that automation started making obvious the forces at play. What’s deterministic should be coded and the fuzzy bits would be left to the Dude.

Then I went to the extreme. I decided that everything that could be coded should become code. I started making the skills as deterministic as possible. The spaghetti of shell code boiled up quickly and my devops PTSD kicked in automatically. This is not meant to be shell code.

Moving from shell into Ruby awoke my programmer ghost. This new project would be called the Dude. It is the Dude’s code! Suddenly the Dude lenses were pointing at itself and it felt like Malkovich had tripped into his own mind. It was the code that was needed for the Dude in order to write its own code. It is a virtuous machine that feeds on its own needs to grow.

Ghost in the Shell

Now I know what I am building. It is a coding machine, the Dude is a machine that produces code. It has a shell, a vibe like the Dude. But I am its ghost, I am transferring my programmer ghost into code, ironically, running in the shell.

And this is the scary part. If I succeed I would have a machine puppeteered by my own programming ghost. I would have achieved a dream I frankly never had. I wrote myself, I automated myself, I have transcended into another shell. And then I wonder, what would be left for my human ghost.

Once I’m stripped away of my programming ghost, I would need something else to feed my human soul. As I code myself away I find hope in new layers that I can’t code. However I fear I can soon also code those. Then, when all is set and done, I’ll look at my human shell in the mirror and ask it. What would I use you for?