Bragibytes
All writing

I Built This Blog by Directing an AI

2 min read
aimetaworkflow

This entire site — the design, the components, the newsletter form, the RSS feed, even most of the writing you’re reading right now — was built by directing an AI.

I didn’t write the majority of the code. I directed it.

What actually happened

I started with a rough vision: “Build me a beautiful, fast, personal devblog from total scratch focused on AI-powered development.”

From there it became a conversation:

  • “Make the RSS link a small icon instead of a main nav item.”
  • “Add a proper email newsletter in the footer.”
  • “This third link still feels off.”
  • “Let’s center the whole blog around AI development.”

At every step I was acting less like a traditional developer and more like a product engineer + architect who happens to have an extremely fast, slightly junior, but incredibly patient implementation partner.

Why I’m writing about this

Most writing about “vibe coding” or “AI-assisted development” is either hype or cope. I want to document the real, slightly uncomfortable middle ground I’m in:

  • The parts that feel like genuine leverage.
  • The parts that still feel like I’m babysitting a very talented intern.
  • The skills that are becoming dramatically more important (direction, taste, system design, evaluation).
  • The skills that are quietly atrophying.

This blog is my public attempt to figure out what “being a developer” even means when most of the typing is no longer done by me.

What you can expect

  • Honest workflow breakdowns (what I actually typed vs what the model did)
  • Post-mortems of projects built this way
  • Techniques that consistently produce good results (and ones that don’t)
  • The psychological side of this transition, which nobody talks about enough

If you’re also in the middle of this shift — between “I write the code” and “I direct the intelligence that writes the code” — I think we’ll have a lot to talk about.

— Sam

P.S. The source is public at https://github.com/bragibytes/devblog. A large portion of it was generated through this exact process. Feel free to dig in.

← Back to all posts
Back to top