← Back to blog

Vibecoding My Personal Website

·7 min read

I built this entire website through vibecoding — collaborating with AI to go from idea to deployed site. Here's what that experience was actually like.

What is Vibecoding?

Vibecoding is a style of development where you describe what you want at a high level and let an AI assistant write the code. You steer the vision, review the output, and iterate. Think of it less like dictating to a typist and more like pair programming with a very fast junior developer who never gets tired.

How It Started

I wanted a personal site that felt like me — a developer's aesthetic with a terminal vibe, interactive AI/ML demos, and a blog. Instead of starting from a blank Next.js template and grinding through boilerplate, I described the vision and let AI scaffold the whole thing.

Personal Reflections

  • There is no replacement for critical human thinking. AI is an augmenter, and a powerful one. The human still needs to know the starting point, the destination and a vision of how to get there
  • Broad technology foundations go a long way in vibecoding
  • The benchmark for productivity has shifted upwards dramatically. What could be done by a team of 10 in 6 months just a few years ago, now can be achieved in less than a day by a guy with a laptop and a Claude Code sub

What Surprised Me

A few things caught me off guard:

  • **Speed**: The initial scaffold — layout, pages, components, styling — came together in a fraction of the time it would have taken manually
  • **Consistency**: Once the AI understood the design system (Tailwind tokens, terminal aesthetic), it maintained that voice across every new page
  • **The 80/20 flip**: Instead of spending 80% of my time on boilerplate and 20% on creative decisions, it flipped. Most of my time went into deciding *what* to build and *how* it should feel

Where I Still Drove

Vibecoding doesn't mean abdicating responsibility. I made every meaningful decision:

  • The terminal/developer aesthetic and code-block bio
  • Which interactive apps to build and how they should teach
  • Content strategy — what to write about and what tone to strike
  • Architecture choices — Vercel over AWS for deployment simplicity

What I'd Do Differently

  • Start with a clearer design system document upfront — the AI works better with constraints
  • Write the content first, build the UI around it, not the other way around
  • Lean into the interactive demos earlier — they're the most valuable part of the site

The Meta Part

Even this blog post was vibecoded. I described what I wanted to say, the AI structured it, and I filled in the parts that needed my actual voice and experience. That's the whole point — AI handles the structure, you bring the substance.

*Built with Next.js, Tailwind CSS, and a lot of conversations with Claude.*