Two Years Later: Not Another Portfolio Refresh

It’s been two years since I last posted here, and honestly, it’s wild to think about how much has happened since then. Time’s definitely been weird, but working at a startup through all the craziness has warped time in its own special way.

In the past two years, life has thrown a lot at me—both professionally and personally—and I figured it’s time for an update. Here are some highlights:

• I started working at my first startup.
• Bought my first house (YouTube University has been my go-to for repairs).
• Adopted a dog.
• Learned a lot about the things I do for work and fun.
• And yep, gave my portfolio a refresh.

Before you roll your eyes about yet another portfolio update, let me explain-this one’s not just about showing off a new design. As a matter of fact, the design is almost exactly the same. (You’ll notice the portfolio section missing as well, stay tuned-we’ll build that in a later post.) It’s more about reflecting on what’s stayed the same and what’s evolved over these past two years.

What Stayed the Same?

Next.js

Still team Next.js here. It’s hands down the most versatile platform I’ve worked with, and it continues to grow in all the right ways. Sure, it has its quirks like any framework, but Next.js gets the job done—whether I’m working on personal projects or dealing with the complexity of startup life.

The App Router was a recent game-changer for me. It’s made Next.js even more adaptable and has been a fun tool to experiment with, making my workflow more efficient.

Tailwind CSS

I’ve also stuck with Tailwind. This framework’s utility-first approach just works, making it quick and painless to go from a basic prototype to something polished and production-ready. I honestly can’t see myself moving away from it anytime soon—it’s become an essential part of my toolkit.

What Changed?

MDX Over Sanity CMS

First off, no shade to Sanity CMS—it’s still a solid platform. In fact, in my day job, I’ve led several migrations to Sanity because it’s incredibly flexible and ticks all the boxes for stakeholders. It’s one of those platforms you can’t help but appreciate when you need a powerful CMS with great support.

That said, for my personal site, I needed something lighter. Enter MDX. MDX is just simpler, which is what I was looking for. I can drop React components directly into blog posts and I don’t have to mess with CMS overhead or schema configurations. It’s exactly what I needed for this refresh—lightweight and efficient.

Vercel Over Netlify

I’ve been a fan of Netlify since 2017 for all my personal projects. It has always served me well, but after transitioning to Vercel with my team over the past couple of years, I couldn’t help but notice how well it fits my current needs.

The biggest thing for me is the UX—it just feels more aligned with what I’m doing now. Netlify’s great, but Vercel’s been the smoother choice for the direction I’m headed.

Final Thoughts

So, there it is—a two-year journey full of growth, new experiences, and of course, another portfolio refresh. If you’re thinking about updating your own portfolio or rethinking your tech stack, hopefully, this gives you some ideas to consider!