Why Losing My Source Code Was the Best Thing for My Portfolio

The "Disaster" That Sparked a Reset

Normally, losing the source code to your personal site is a developer's nightmare. But when it happened to me, I realized something surprising: I was actually excited. It forced a full reset. Instead of desperately trying to restore an old backup, I saw a massive opportunity to embrace change and rethink what my site was actually supposed to achieve.

The Old Mindset: The Digital Museum

My previous site was a solid Next.js + Chakra UI build. It did its job, but looking back, my mindset was purely transactional. It was a digital museum—just a list of finished products behind glass. There was no room to document my growth, no space to talk about the why behind the code, the bugs that kept me up at night, or the "aha!" moments of learning new architectures.

The Mindset Shift: Building for the Journey That clean slate changed how I view building applications. I realized that an engineer's true value isn't just in the polished final product; it's in the resilience and problem-solving it took to get there. I didn't want a static portfolio anymore. I wanted a platform that lives, breathes, and evolves right alongside me.

What's Different Now

In this rebuild, the blog is no longer an afterthought—it's a first-class citizen. Sure, my projects still get their showcase cards, but the real depth lives right here in these posts. This is where I'll be sharing the gritty debugging stories, the architectural decisions, the dead ends, and most importantly, the growth that comes from solving hard problems.

I couldn't be more optimistic about this next chapter. The code is brand new, but the mission is much bigger. Welcome to the journey!