I built my portfolio because I was tired of just saying I can do stuff. Yeah, I can code, design, think product — but where's the proof? I needed something that actually shows what I can do instead of just listing it on a CV.
The hardest part wasn't even the coding. It was deciding what to show. I kept overthinking everything — "is this project good enough?", "does this look clean?", "does this actually represent me?" — that part slowed me down way more than anything technical.
There's something uniquely exhausting about trying to present yourself. You know too much about every flaw. You see the shortcuts you took and the things you wish were better. Imposter syndrome doesn't care that you built the thing — it just asks whether it's good enough.
"Is this project good enough? Does this look clean? Does this actually represent me?"
— Every hour of overthinking, condensed.
The most painful moment? Breaking the entire layout over one tiny CSS change, then spending hours trying to figure out what went wrong — just to realize it was one line. Classic.
That's the thing about building in public, even if "public" just means a GitHub Pages URL at first. Every broken layout is a visible failure. Every deploy that looks off is something a recruiter could theoretically see. It adds a pressure that a private project just doesn't have.
But what I'm most proud of is the overall vibe. The design, how everything flows — it actually feels like me, not some template I copied. And getting it live? That moment when you refresh and it's just there on the internet?
That hit different.
It's not perfect. But it's real. And that's kind of the point — shipping something imperfect and true beats waiting forever for something flawless that never leaves your laptop.
If you're sitting on something you built, waiting until it's "ready" — just push it. The internet has seen worse. And you'll fix it as you go.