An equation, a circuit, and a city can seem like entirely different things. Look a little closer, and each becomes a way to ask the same question: how do the parts fit together? That question is the thread connecting science, engineering, and the things I want to build.
Start with a better question
There is a difference between recognising an answer and understanding why it works. A formula can be familiar without being useful. The useful moment comes when you can explain its assumptions, draw a picture of what it describes, and say where it stops applying.
In physics, that might mean checking a limiting case. In engineering, it might mean asking what happens when a component is imperfect. In a product, it might mean watching someone try to use it without instructions. Each approach brings an abstract idea back to something observable.
The more carefully we look, the more there is to understand.
Move between scales
Engineering makes that movement particularly tangible. A small change in a circuit can alter the behaviour of an entire system. A decision about software architecture can determine whether a product remains easy to maintain. The details matter because they accumulate.
At the same time, focusing only on the details can hide the purpose of the work. Before optimising a part, it is worth asking what the system is meant to accomplish. A beautifully engineered solution is still incomplete if it solves the wrong problem.
Keep a record of the process
A notebook offers a place to preserve more than conclusions. It can hold the diagram that finally made sense, the experiment that did not behave as expected, and the question that is still unanswered. Those are often the most useful parts to return to.
This is the kind of record I want to build here: notes that connect what I study with what I make. Some will be technical. Others will follow an idea into books, business, or the streets of a new city. The common aim is to understand a little more, then do something useful with it.
