Agentic Development
Building This Website with AI Agents: A Meta Case Study
How I used agentic development to build this site, what worked well, and where human judgment still mattered.
Using agentic development to build a website about agentic development is a little on the nose, but it was the right project for it.
This site was built with an AI coding agent as part of the workflow. I don’t mean that in a vague marketing sense. An agent handled a real amount of the implementation work while I steered, reviewed, and pushed the design where I wanted it to go.
What the agent helped with
The agent was useful for the parts that usually create friction:
- Scaffolding the site structure
- Creating and revising templates
- Wiring up layouts and content sections
- Making broad style changes across the site quickly
That is the kind of work where agentic tools shine. You can describe the direction, let it take a pass, then decide whether it got you closer or farther away.
What did not work
The first version of this site looked too generic. It had the usual signs: polished gradients, trendy cards, and design choices that felt like they came from the same bucket as every other AI-generated landing page.
So I changed it. The value was not in accepting the first output. The value was in being able to move quickly through bad versions until I got to something that actually felt like me.
The same thing happened with the writing. Early drafts were fine mechanically, but they did not sound like me. Too polished, too abstract, and too many phrases no real person would choose on purpose.
The takeaway
Building this site with an agent did not feel like pressing a button and getting a website. It felt more like working with a very fast junior engineer who can do a surprising amount, occasionally makes weird choices, and absolutely needs review.
That is still useful. Probably more useful than most of the current AI marketing would suggest.