Why We Build Things

There is a pervasive attitude in backend engineering that aesthetics are secondary. The logic often goes: If the API returns a 200 OK within 50ms, who cares what the JSON structure looks like? If the system scales to a million users, does the dashboard’s typography really matter?

I used to think this way. Then I realized that engineering is essentially a form of communication.

The Architecture of Empathy

Whether you are designing a public-facing product, an internal developer tool, or simply a CLI script, you are building an interface for a human being. The care you put into how that interface feels is a direct reflection of your empathy for the user.

When we talk about “beautiful code,” we’re usually talking about readability and structure. But when we talk about a “beautiful product,” we are talking about trust.

Users instinctively trust things that look well-made. A stark, unformatted error message tells the user “We didn’t care enough about this edge case to design for it.” A carefully crafted, monochromatic, high-fidelity experience says “We care about every detail, which means we probably cared about the security and performance of your data, too.”

The Storytelling Aspect of Code

In my portfolio, I recently redesigned the entire tech stack section to look like a mechanical Orrery in a notebook, instead of just a grid of icons. Functionally, it does the exact same thing: it tells you I know React, Node, and AWS.

But narratively? It tells you that I view technology as an interconnected, mechanical system. It tells you I care about the craft.

We build things because we want to solve problems, yes. But the best engineers build things because they want to tell a story about how the world should work. Don’t let the aesthetics be an afterthought. They are the vocabulary of the story you are trying to tell.