Embracing Simplicity

I recently redesigned my portfolio website, and the biggest change wasn't adding more features. It was taking things away. I wanted something clean, minimal, and focused on content rather than flashy design elements.

The inspiration came from sites like leerob.com, which prove that simplicity doesn't mean boring. It means intentional. Every element has a purpose. There's no clutter competing for attention.

Why Minimal?

As engineers, we often fall into the trap of over engineering. Not just our code, but everything we build. We add features "just in case" or because we can. But the best portfolios aren't about showing off every trick in the book. They're about clearly communicating who you are and what you do.

A minimal design forces you to be deliberate. What actually matters? For me, it's my experience, the projects I've built, and the technologies I work with. Everything else is noise.

What I'm Learning Next

Right now, I'm going deeper into two areas that fascinate me: Rust and PostgreSQL.

Rust appeals to me because it challenges how I think about performance and safety. Coming from Python and TypeScript, Rust's ownership model is a completely different paradigm. It's hard, but that's exactly why it's worth learning.

PostgreSQL is something I use every day at work, but I want to understand it at a much deeper level. Query optimization, indexing strategies, partitioning, replication. There's so much depth there. I want to move beyond just writing SQL queries to truly understanding how the database thinks.

Moving Forward

This blog is part of that journey toward simplicity. No comment systems, no analytics dashboards, no engagement metrics. Just writing about what I'm learning and building.

Sometimes the best way forward is to strip away the unnecessary and focus on what matters.