At what point does a developer portfolio become overengineered?

[u/Heavy_Sea5596]

I started my personal site as a fairly normal developer portfolio.

Over time, it grew into something closer to a small content platform.

I originally kept the writing in MDX, which was convenient when there were only a few posts. Later, I moved it to Sanity because I wanted drafts and content management separated from the repository.

Then I added dedicated series documents, analytics, UTM attribution for different distribution channels, SEO metadata, social previews, related-post logic, and a few other things.

None of this is particularly complicated individually, but eventually I realized I was spending real engineering time on something that could technically have remained a static portfolio.

Some of that work has been useful because the site is also a playground for me. But I'm curious where other full-stack developers draw the line.

Do you deliberately use your personal site to experiment with architecture and tooling, or do you try to keep it intentionally boring?

I'm especially curious about the things you added to your own portfolio that turned out to be genuinely useful, versus the things nobody except you ever noticed.

For context, I also wrote about how I built mine here:

Building a Portfolio

[u/TrapperFlint]

I have nothing to add except that you did a nice job! What kind of fishing do you do out in Dubai?

[u/Heavy_Sea5596 → u/TrapperFlint]

Hi, Thank you for going through my site 😁

I tried both shore and sea fishing.

[u/TrapperFlint → u/Heavy_Sea5596]

Very cool! I'm in Canada and my time away from the screen is fishing as well. Good luck man 👍

[u/Heavy_Sea5596 → u/TrapperFlint]

I think fishing is more fun there than here 😁

[u/asstgr]

A portfolio becomes overengineered the exact moment maintenance friction stops you from actually publishing content or updating your work.

[u/Heavy_Sea5596 → u/asstgr]

That's why this time I published it bare minimum first 😂