From HR to Vibe-Coder: How I Built My First Website in 3 Days

The past four weeks, I've been shared the basics of AI, prompting techniques, the 5 Pro Tips framework, how to treat AI like a fresh hire you need to give clear instructions to. It was all theory. Let's put it all together, by sharing what I have done on a slightly bigger scale So I decided to create my own personal website. No coding background. Just years of experience in HR and a stubborn curiosity about what's actually possible now. The Fear Was Real I'll be honest, I was terrified. I have heard the term "vibe coding" thrown around but had no idea what it meant. The thought of AI writing code and doing things to my computer made me uneasy. What exactly is it doing? What if it breaks something? I felt like I was handing over the keys to my laptop without understanding where it was going. I didn't know where to start. Every tutorial assumed some baseline knowledge I didn't have. Every forum discussion felt like people speaking a different language. But I pressed on anyway. Finding the Right Tool After some research, I landed on Google Antigravity, a brand new AI-powered IDE that Google released just a couple of months ago. It's designed to let AI agents handle the heavy lifting of coding while you guide them with instructions. The timing felt right. A new tool, a fresh start, no baggage of "you should already know this." I have also decided to use two AI assistants side by side: Claude and Gemini. Not because I planned it that way, but because when one got stuck, I would ask the other. Different perspectives, different approaches. The Prompting Foundation Paid Off Here's what surprised me most: it wasn't as hard as I expected. Learning prompting in the past? They mattered. When I gave clear, specific instructions, the AI understood what I wanted. When I was vague, I got vague results. The skills transferred directly. Treat the AI like a fresh hire. Be explicit. Give context. Check the work. The Frustrating Part (There's Always One) The most maddening moment? When the AI kept suggesting the same solution for the same error. Over and over. Like a broken record. I would try the fix. It wouldn't work. The AI would suggest... the exact same thing again. That's when I learned to change how I prompted. Instead of just saying "that didn't work," I started describing what happened, what I expected, what the error actually said. I gave it more context to work with. Breaking out of those loops required me to think differently about the conversation. Not just asking for answers, but guiding the AI toward new directions. Getting Comfortable With the Unknown My fear of not knowing what AI was doing to my computer? It faded, but not because I stopped caring. I got comfortable by asking questions first. Before letting the AI run any code, I would ask it to explain what it planned to do. I would verify what I understood before giving the go-ahead. That simple habit, understand first, then execute, made all the difference. I wasn't blindly trusting. I was collaborating. Three Days Later I had a website. A real one. With a portfolio section, an about page, and a blog where you're reading this right now. I'm not going to pretend it's perfect. I'm not going to claim I suddenly understand programming. But I built something. From nothing. In three days. And honestly? I'm proud of myself. What I'd Tell You If you're in HR, marketing, operations, any field that isn't "technical, and you've been curious about building something but felt like it wasn't for you: Start small. Don't try to build the next big app. Don't compare yourself to developers with years of experience. Pick one tiny thing you want to create. A simple page. A basic tool. Something manageable. The AI tools available now are designed for people like us. People who have ideas but not the coding vocabulary. People who can communicate clearly and think through problems, even if we can't write a single line of JavaScript. Those skills you've built in your career? The ones about giving clear briefs, managing expectations, iterating based on feedback? They transfer directly to working with AI. You already have what it takes. You just need to start.