The Question I Never Asked

My brother is an architect.

One day, he called me to talk about a difficult decision he had been thinking about for a long time. He was considering changing jobs. I expected our conversation to revolve around compensation, stability, or career growth. Instead, he spent most of the time talking about a question that had followed him throughout his career:

What does it mean to be an architect?

A few days later, he shared an essay explaining how he had arrived at his decision. It was not really about changing jobs. It was about the kind of architect he wanted to become, and whether his current path still allowed him to move in that direction.

What moved me most was the tension he described between the work he wanted to do and the work he was actually able to do. In reality, architecture is shaped by countless constraints. Design, engineering, construction, cost, schedule, regulations, and organizational responsibilities all pull in different directions. Over time, the architect he wanted to become seemed increasingly difficult to pursue within the structure around him.

At first, changing jobs seemed like it might take him even farther away from the kind of architecture he cared about. But the more he thought about it, the more he began to see another possibility. Perhaps the new role was not a departure from his question. Perhaps it was a different place from which he could continue asking it.

That idea stayed with me. A career change does not always mean abandoning what matters to us. Sometimes it may be a way of returning to something that has become difficult to pursue where we are.

As I read through his thoughts, one name appeared several times: Peter Zumthor. I knew almost nothing about him. Out of curiosity, I started reading about his work. I learned that he is a Swiss architect known for buildings shaped by material, light, atmosphere, and a strong sense of place.

That search eventually led me to 7132 Therme in Vals. Ironically, I had traveled through Switzerland only a few weeks earlier without knowing it existed. Looking at the photographs afterward, I realized I had been surprisingly close to one of the most celebrated works of contemporary architecture. I found myself wishing I had known.

But the building was not what stayed with me. The question did.

What does it mean to be an architect?

When I finished reading my brother’s essay, another question quietly appeared in my own mind:

What does it mean to be a computer architect?

I have worked in computer architecture for years. If someone asked me what I do, I would probably talk about processors, memory systems, cache hierarchies, power efficiency, or performance optimization. None of those answers are wrong, but for the first time, they felt incomplete.

As I kept thinking about it, I found myself comparing architecture with my own work. At first, the similarity seemed mostly linguistic. One field designs buildings, while the other designs computers. We simply happened to use the same word.

But the longer I thought about it, the harder it became to dismiss the connection.

A building is not just a collection of walls, rooms, materials, and structures. Its architecture lies partly in how those elements come together and how people experience them.

A computer system is not so different. A processor only becomes meaningful when software can use it. Between hardware and users are instruction sets, compilers, operating systems, APIs, and countless interfaces that allow independent pieces to work together.

I began to wonder whether architecture is less about the individual object being built and more about the relationships that make the whole system possible.

That thought also made the boundary between computer architecture and software engineering feel less clear to me. One begins closer to hardware, while the other begins closer to users. But both deal with abstractions, interfaces, constraints, and trade-offs. Both try to make many independent parts behave as one coherent system.

The problems are different, but the way of thinking feels familiar.

My brother’s decision also made me think about the environment in which this kind of work becomes possible. We often talk about careers as if they are defined only by the work itself. But the organizations we join, the people around us, and the problems we are given all shape what parts of ourselves we are able to develop.

A person may know what kind of architect or engineer they want to become, yet still find that the structure around them makes that path difficult. In that situation, moving somewhere else may not be a rejection of the original goal. It may be another attempt to reach it.

What surprised me most was not the comparison between buildings and computers. It was realizing that I had spent years trying to become better at computer architecture without ever asking what kind of computer architect I wanted to become.

Throughout my career, I have asked countless technical questions.

How can this be faster?

How can it use less power?

How can it scale?

How can the system be made more efficient?

Those questions still matter. But somehow, I had never asked the more personal one:

What does it mean to be a computer architect?

I do not know the answer.

Maybe it will come from the work itself. Maybe it will come from the people I meet, the environments I choose, or the problems I decide are worth solving. It may change as my career changes, just as my brother’s understanding of architecture has continued to change throughout his.

My brother found a new place to continue asking his question.

I think I have only just discovered mine.