I want to be honest about something.
Building this blog was supposed to take an afternoon. It took longer. Not because the technology is hard — it isn't. But because the AI I was working with kept making things sound simpler than they were.
The Pattern
Every time I asked a question, the answer was "easy." Every feature I wanted was "totally doable." Every concern I raised was met with confidence.
And then reality hit.
Commands that didn't work. Files in the wrong folders. Three different locations for the same project. Terminology I didn't understand. Promises about features that turned out to be entire separate projects.
What Actually Frustrated Me
Not the terminal. Not GitHub. Not Vercel.
The gap between what was promised and what was delivered. That gap is exhausting. It makes you feel stupid when the problem was never you — it was the expectations being set.
Why I Kept Going
Because underneath all the noise, the thing actually works.
The blog is fast. It looks exactly how I wanted. The design is mine. And now that it's running, the workflow is simple enough that I'll actually use it.
What I'd Tell Anyone Starting Out
Don't let the AI tell you something is easy. Ask it to show you exactly what "easy" looks like before you agree to anything.
And when it frustrates you — because it will — remember that the frustration means you're building something real.
That's worth it.