Why I Built Another Portfolio Even Though I Already Had One

I already had a portfolio before this one. It worked fine and it did what I originally wanted it to do. It had projects, experience, blogs, and the usual things expected from a developer portfolio.

Over time I started feeling limited by it.

The old portfolio was built around the idea of listing everything I had worked on. At that stage of learning software development, that made sense to me. I thought a portfolio should contain all projects, all experience, and every important thing in one place.

That mindset slowly changed.

As I spent more time building things, contributing to open source projects, exploring developer tooling, fixing bugs, and working on real applications, I realized most platforms already solve parts of that problem very well.

If someone wants to see all my projects, GitHub already does that better.

If someone wants to check my experience, volunteering work, or certifications, LinkedIn already handles that properly.

Trying to duplicate those platforms inside a portfolio started feeling unnecessary.

I also started doing things that did not fit properly into the old structure. Open source contributions, experiments, automation tools, package development, bug fixes discovered while exploring software, and random technical thoughts slowly became a bigger part of my work. The old portfolio was not designed for that kind of growth.

This new portfolio is built with a different mindset.

Instead of trying to display everything, it focuses on showcasing the most meaningful work and directing people to the right places depending on what they want to explore further. Projects can point to GitHub. Experience can point to LinkedIn. Blogs can exist independently without forcing everything into one large collection page.

I also wanted something easier to evolve over time. If my interests shift later into something else, I can create new sections without rebuilding the entire structure again.

Another reason behind rebuilding this portfolio was the engineering side of it. I wanted a system that was easier to maintain and extend. The new portfolio includes a markdown powered blog system, dynamic metadata generation, SEO improvements, structured data, reusable rendering systems, and a more flexible architecture compared to my previous one.

This project was also built with the help of AI tools during development. AI helped speed up parts of implementation, UI iteration, and templating. The engineering decisions, debugging, architecture planning, optimizations, and problem solving were still handled manually throughout the project.

I do not see AI as a replacement for engineering. I see it as another tool that can speed up development when used properly.

At the end, this portfolio is not meant to be a complete archive of everything I have ever done. It is a smaller and more focused representation of where I currently am as a developer and the kind of work I enjoy building today.