Vibe Coding and the Art of Building Without Really Building

There's a new way of making things on the internet, and it doesn't have a great name yet. Some people call it vibe coding — the practice of building software by describing what you want and letting an AI write the actual code. You're less a programmer and more a director. You have the vision. The AI has the syntax.

This site is one of those projects.

How It Actually Works

I didn't write most of the code here. I described what I wanted — a simple personal site, a blog powered by Markdown files, clean design, easy to update — and an AI put it together. When something broke, I described the error. When I wanted social media icons, I asked for them. When the date field threw a runtime error, I said "fix this" and it got fixed.

The whole thing took less than an hour.

That used to feel like cheating. Now it feels like the most honest way to build something when your goal isn't to become a better programmer — it's to have a working website.

What Vibe Coding Is (And Isn't)

Vibe coding isn't magic, and it's not a shortcut to understanding. If something goes seriously wrong, you still need to be able to read the error, describe it clearly, and know whether the fix makes sense. You're not off the hook entirely.

But it does change the barrier to entry dramatically. The gap between "I have an idea" and "this exists on the internet" used to require learning a stack, setting up a dev environment, debugging configuration files, and understanding the difference between a framework and a library. Now it requires being able to say what you want in plain language.

That's a real shift.

The Nature of This Project

This site exists because I wanted a place to write things down. Not a social media post. Not a thread. An actual page on the internet that I own, that I can update whenever I want, without an algorithm deciding who sees it.

The blog runs on Markdown files. To publish something new, I create a file, write in it, and push it to GitHub. The site rebuilds automatically. There's no dashboard, no editor, no login screen. Just files and words.

It's a simple system. That's the point.

Does It Matter Who Wrote the Code?

I've thought about this. The honest answer is: it depends what you're optimizing for.

If the goal is to learn to code — then yes, having an AI write everything defeats the purpose. But if the goal is to have a thing that works, the authorship of the underlying code matters about as much as whether you built your own keyboard to write with.

I'm using this site to think out loud. The code is the vessel, not the point.

Vibe coding lets non-technical people participate in the web as builders instead of just consumers. That seems worth something.