Why I Created My Blog and How I Did It in 2 Hours
TL;DR: I built my entire website (blog + typing game + portfolio) in 2 hours using Claude Code. The secret? Know exactly what you want before you start, and use AI as your fingers, not your brain.
What to expect:
- Why I finally decided to create a blog
- How Claude Code changed my development workflow
- Lessons learned from building with AI
Introduction
Hey there. My name is Giovane, and this is the first of many blog posts.
I always wanted to create a blog, but I never had the time to do it.
I am not a lazy person, but let's be real, if you have a full-time job, a wife, and a family, if you're a family guy like me, it's impossible to build cool stuff outside work if you don't sacrifice time with one of them.
But, we live in the AI agents era, so I finally decided to create one, and I'll talk about the motivation and how I did it using Claude Code.
The Motivation: Why I Finally Decided to Create a Blog
I switched gears after I finished my mechanical engineering degree. I really love engineering, but I didn't like the mechanical part of it. Of course, I learned a lot of cool stuff in physics and math, but in my internship, I realized that this was not what I wanted, and the reason was really simple, it's really hard to find a job in that field where I live, a small town in the state of São Paulo.
If you want to find something that will pay you a decent amount, you need to leave. For me, that was not an option, so I needed to find something that aligned better with my goals.
Then, I started to look for other options, and I heard about the "remote work". In that moment, I realized that this would be my first goal.
When you're a guy like me, with no background, no prestigious universities, no big tech companies on the resume, no connections, no nothing, you need to find your way.
So, for me, the best way to prove to people that I know what I do, is to build in public and create good content, who knows if I will help someone in the same place as I was.
Why a blog?
I always liked blogs, I find them cool, especially technical ones.
When you're not in a company that has engineering blogs, or you don't work in something public/open source, it's really hard to show people what you do.
So, what's better than writing technical and career posts?
Claude Code for development
I found out about Claude Code about 6 months ago. And it was the best thing I could've discovered.
For those unfamiliar, Claude Code is an AI-powered coding assistant that lives in your terminal. You describe what you want to build, and it writes the code for you.
While most people see Claude Code as "a replacer for devs" and have fear of it, I only see it as a tool and an opportunity to ship cool stuff, within a time that was impossible before.
Why is that? Because I use Claude Code as my fingers, not my brain.
Of course, I talk with Claude to ask for guidance sometimes, but I don't use it in YOLO mode. I like to know what is being built, especially in my work environment.
When you learn how to use it, it's a no turning back moment.
The Development Process: Building It
The process was simple. I had the idea in my mind, and I knew how to execute it. I knew exactly what I wanted and how I wanted, which components to use, patterns, techs, so I created a plan for Claude to follow.
Using the plan mode, I talked with it a little bit about my choices, and possibly identifying bottlenecks, and after 2 hours of talking, I had everything I needed: skills, agents, and a plan.
After that, I just guided Claude to build it.
How Claude Code Changed Everything
I built the entire website, with a typing roguelike game, a career timeline, and a blog, in 2 hours.
That is IMPOSSIBLE to build alone.
Especially for me, with no previous game development experience.
Even if you're a guy who writes 3000 lines in 5 seconds in neovim, you're not making it.
But now that I have the fast fingers to build that, I just need to review the output.
Of course, you don't build that in 2 hours if you watch for every step, so I just let Claude do it and validated everything visually.
But, DO NOT do that at work, trust me. Always validate the code yourself.
Working With AI as a Development Partner
The key to working with Claude Code is simple: you need to know what you want.
I see a lot of people complaining that "AI doesn't work" or "it keeps doing the wrong thing." And most of the time, the problem is that they don't know what they want. They just throw vague prompts and expect magic.
That's not how it works.
Before I started building this website, I already had everything in my head:
- Stack → Next.js, Tailwind, shadcn/ui
- Pages →
/blog,/about,/game - Components → The structure, the patterns
- Architecture → How everything connects
Claude Code didn't decide any of that. I did.
What Claude Code did was execute. Fast.
I used plan mode to validate my architecture choices, created skills to automate repetitive tasks (like creating new blog posts), and ran multiple agents in parallel to build different pages at the same time.
The secret? Treat it like a really fast co-worker who never gets tired. You give clear instructions, you review the output, and you iterate. That's it.
I do use Claude to help me think through problems - that's what plan mode is for. But I don't trust it blindly. I validate, I question, and I make the final calls.
The AI proposes, I decide.
Lessons Learned
I learned a lot with this project:
- Running multiple agents → I built
/aboutand/gamepages in parallel - Using skills → Automating repetitive tasks like creating blog posts
- Prompting better → Being specific about what I want
- Pro plan limits → The Pro plan ran out faster than expected, so I upgraded to Max. If you're building seriously, budget for it.
Conclusion
To be honest, I did this in kind of a rush. I just want to deploy this website fast and let people play the typing game.
I hope that helped you learn something. If you want to chat, feel free to reach out.
That is the first of many posts, I promise.
If this post was helpful, consider leaving a like. It helps me know what resonates with you.
Farewell!