I Had to Build My Portfolio to Realize I Already Had One

That sounds stupid at first, but it is exactly what happened.

For most of my working life, I thought about my portfolio as something I could not really show. Maybe because it was not impressive enough, or at least that is what I used to think.

I come from freelancing, and in freelancing, especially when you work with small businesses and entrepreneurs, projects do not always look like clean case studies. Most of the time, someone needs something specific, you solve it, the project works, the client moves on, and then they disappear into the same mysterious dimension where old requirements, unpaid revisions, and “just one small change” probably live together.

So for a long time, I thought: maybe this does not count as a portfolio. Maybe this is just work. Useful work, real work, but not the kind of work you put on a personal website to make yourself look serious on the internet.

But while I was rebuilding my website and organizing my projects, something became obvious: the portfolio was already there. It was not missing; it was scattered.

It was inside the websites I built, the platforms I helped launch, the interfaces I designed, the systems I maintained, the production problems I solved, the clients I guided, the technical decisions I made, and all those small invisible moments where a project only survives because someone understands both the code and the chaos around it.

Rebranding Is Not Always Decoration

That changed the way I started thinking about rebranding.

Maybe rebranding is not always about changing colors, typography, images, or making everything look more “premium”, whatever that means in the great museum of corporate nonsense.

Sometimes rebranding is simply the process of looking at your own work with enough distance to understand what it actually says about you.

And that is uncomfortable, because it forces you to stop treating your work as a pile of finished tasks and start seeing it as a body of decisions.

A project is never just a screenshot. It carries context. It carries constraints. It carries mistakes, compromises, priorities, pressure, and a thousand tiny choices nobody sees once everything is live.

That is where the real value often lives.

Not only in the final interface, but in the judgment behind it.

Storytelling as Structure

That is where storytelling becomes important.

Not storytelling as decoration. Not storytelling as a nice emotional layer you add at the end to make something look deeper than it is. We already have enough of that floating around the internet, usually next to a photo of someone looking thoughtfully at a laptop.

I mean storytelling as structure.

A way to connect what seems fragmented. A way to give context to decisions. A way to show the relationship between experience, judgment, product thinking, design, business, SEO, performance, architecture, and the human mess behind every real project.

Because a portfolio without storytelling is usually just a list: technologies, clients, screenshots, dates, responsibilities.

Technically correct, yes.

Also very easy to forget.

A story gives those pieces direction. It explains why something mattered, what problem existed, what decisions were made, what changed, what was learned, and what kind of professional was behind the work.

That was the part I was missing.

I had the experience, the projects, the stack, the years working in software, my photo, my texts, and that whole professional inventory we arrange so the internet can say: “ok, this person apparently exists.”

But the information alone was not enough.

It needed a narrative.

People Do Not Dig, People Scan

When someone enters your website, they are not calmly reading everything as if it were a Russian novel.

They enter, look, interpret, and decide in seconds.

The image, the headline, the first paragraph, the preview that appears when you share the link; all of that is already telling a story before someone reaches your projects.

And if you do not shape that story, people will create one for you.

Usually a lazy one, because humanity apparently chose speed over depth and then called it user behavior.

That is why I started working on the share image, the initial narrative, and the way my website presents what I do.

Not to pretend I am a different kind of professional, and not to dress my work as something more glamorous than it is, but to create more coherence between what I have built and how it is perceived.

More Than Code

I build software, yes, but I also think about product, experience, communication, performance, SEO, structure, architecture, and how an interface can make something complex feel simple.

Those things are not always visible, but they shape the final result. And when they are missing, people feel it, even if they cannot name it.

That is also why I rebuilt part of my website: to make it more than a place where my projects are listed. I wanted it to feel closer to how I actually approach software, with attention to product, interface, performance, SEO, architecture, and the small details that make digital products feel intentional instead of just assembled.

If you want to see that work, the new version of my portfolio is here:

vicentechiriguaya.com

Understanding the Work

Maybe the real value of building my portfolio was not just having a place to show my work.

It was finally being forced to understand it.

To look at everything I had done and realize that the story was already there; I just had not taken the time to organize it properly.

And maybe that is the point of storytelling in personal branding: not inventing a better version of yourself, but finding a clearer way to explain the one that has been building, failing, solving, learning, and improving for years.

Because good work still needs to be communicated well.

Annoying, but true.

The world almost never understands anything unless you present it properly.

— Vicente