Like many engineers, I've decided to build my own personal portfolio. It took many iterations and more second-guessing than I expected.

It also took a surprising amount of emotional energy to get it into a shape I was happy to publish. Even so, the time and friction were worth it.

Building your own portfolio might be one of the hardest things you can do. You get so ambitious that you lose sight of the actual goal.

I care about all sides of engineering. I want to use this platform to document my journey as a Software Engineer and showcase my projects (hopefully not the dead ones 👀).

Why a blog?

Writing forces you to think clearly, and that ends up helping the reader as much as it helps you.

Ever had a concept that made perfect sense in your head, only to struggle when explaining it to someone else? I've hit that more times than I'd like, and writing it out is usually what fixes it.

I want to use this blog to explain concepts and work through engineering problems - algorithms, data structures, networking, maths, certifications, and whatever else I'm learning at the time.

I'll also share what I pick up across different domains, from Frontend to Backend, DevOps, Cyber Security, and Database Management.

One last thing

There's a lot to learn and a lot to share. The plan is simple: keep learning, keep writing, and don't stop.