HOW IT STARTED.
It began with a blank Notepad file and a few lines of HTML — no styling, no framework, just raw curiosity. I don't remember exactly what made me type that first tag, but I remember the feeling when it worked. That small moment of "wait, I made this?" was enough. From there, JavaScript followed, and the curiosity never really stopped.
HOW I THINK
I'm a planner before I'm a builder. References first, structure second, then I dive in. But once I'm in, I'm in — I have a bad habit of chasing bugs past midnight just because the loose end bothers me. I'm working on it: timers, schedules, intentional breaks. Still perfectionistic about the small details though — that part I'm keeping.
BEYOND THE SCREEN.
When I close the laptop, you'll probably find me watching One Piece, or going down a K-R&B rabbit hole. I grew up on Age of Empires and Warcraft III — strategy games where every decision compounds. Looking back, maybe that's not so different from how I approach building things.
Watching One Piece
K-R&B Rabbit Hole
Age of Empires III
Warcraft III
WHERE I'M HEADED.
I want to be genuinely good at this — not just functional, but expert-level. The kind of developer who understands not just how things work, but why they're built that way. Eventually, I'd love to work somewhere that pushes that standard. Big ambitions, one commit at a time.
