Why I Changed My Portfolio UI Into a Systems Journal

I changed my portfolio UI because it was no longer helping me communicate the kind of engineer I actually am.

The site already worked. It had projects, writing, contact pages, language support, and a polished enough presentation. But it still felt too close to the default shape of modern personal sites: visually competent, structurally familiar, and not specific enough about the kind of work I want to be trusted with.

That was the real problem.

I do not want my portfolio to feel like a generic personal brand page. I want it to feel like evidence that I design reliable systems, make sound engineering decisions, and can explain complex work clearly. That was the thesis behind the redesign brief I wrote for the project, and it changed how I evaluated every part of the interface.

The old UI was not bad, but it was saying the wrong thing

This redesign was not driven by "the site looks bad." It was driven by "the site signals the wrong things."

That distinction matters.

A lot of portfolio UI patterns optimize for polish before they optimize for trust. They show taste, but not judgment. They show motion, but not evidence. They show tools, but not consequences.

For an engineer, that is a weak trade-off.

If I want someone to believe I can work on financial systems, operational tooling, performance-sensitive flows, or architecture decisions, the interface needs to make those abilities legible. It should not force the reader to infer them from decorative cards, oversized controls, or vague project summaries.

The redesign brief made that explicit. The new direction was "Systems Journal": a restrained, publication-inspired portfolio that feels more authored, more human, and more technically credible.

What changed in practice

The biggest shift was not a new color palette. It was a new frame.

I moved the homepage away from "here is my profile" and toward "here is a structured record of engineering work."

That showed up in a few concrete decisions.

First, the navigation became compact and intentional. The header now uses numbered labels like 01 Work, 02 Notes, 03 Profile, and 04 Contact, with theme and language controls treated as utilities instead of personality features. I also removed the larger preferences panel and replaced it with a much smaller language toggle beside the theme toggle. That reduced interface noise immediately.

Second, the hero stopped trying to impress and started trying to clarify. It now focuses on positioning, current context, calls to action, and proof points. Instead of generic claims, it surfaces measurable results like weekly processed volume, active users, and the query-time reduction from more than 60 seconds to under 600 milliseconds.

Third, the homepage now gives the featured work real editorial weight. The public transportation financial platform is presented as a case study with system context, operational problems, engineering decisions, and measured outcomes. That is much closer to how I want technical work to be understood. A project is not just a card. It is a system, a constraint set, and a sequence of trade-offs that produced a result.

Fourth, the visual language became more restrained. The redesign moved toward warm editorial surfaces, thin borders, compact labels, rectangular panels, and a layout that feels closer to technical publishing than to a startup landing page. I explicitly wanted to avoid glowing gradients, fake terminals, glassmorphism, floating cards, large badge clouds, and unfinished controls.

Why this direction fits my work better

A portfolio is not neutral. Its structure implies what the author values.

If the interface emphasizes decoration, visitors remember decoration. If it emphasizes context, evidence, and decisions, visitors remember the work.

That matters a lot to me because the work I want to highlight is not primarily "I can make nice screens." It is "I can modernize software, improve reliability, reduce operational friction, and explain why specific technical choices mattered."

That is why the featured case study matters. That is why the evidence section matters. That is why the homepage index matters. That is why the copy became more explicit about reliability, performance, and operational clarity.

The redesign also forced me to stop treating every section as equally important. They are not. If I want someone to understand me quickly, the site should front-load the strongest evidence, not the safest biography.

Why I think other engineers should make a similar change

I do not think every engineer should copy this exact visual style.

I do think many engineers should question the default profile UI they are still using.

Too many engineering portfolios are optimized to be pleasant instead of convincing. That is fine if the goal is simply to have a nice online presence. It is weak if the goal is to communicate technical judgment.

If your site still leans on large decorative hero treatments, vague project cards, technology clouds, generic "about me" copy, or controls that are louder than the content itself, the UI may be underselling the actual quality of your work.

The better question is not "Does my portfolio look modern?"

The better question is "Does my portfolio prove the kind of engineer I am?"

For many engineers, that should lead to a different interface:

• less decoration
• better hierarchy
• more context
• more measurable outcomes
• clearer technical decisions
• fewer elements that do not earn their place

That does not mean every portfolio should look like documentation. It means every portfolio should decide what it is trying to prove.

The real lesson for me

This redesign changed more than the homepage. It changed the standard I use to evaluate interface decisions.

Now, when I look at a section, a control, or a visual treatment, the first question is not "Does this look good?"

It is:

• Does this help explain what I built?
• Does this make the work easier to trust?
• Does this create signal or just surface area?
• Does this clarify technical ability or distract from it?

That is a better design filter for an engineer's site.

A portfolio should not just display work. It should frame work correctly.

That is why I changed my portfolio UI. And if your current portfolio still looks more like a generic personal product than a record of engineering judgment, I think it is worth changing yours too.