Machines
I have always been drawn to machines where the engineering is close enough to the surface that you can feel the decisions somebody made. Change bore and stroke and the character of an engine changes. Move where fuel is introduced, change valve area, alter scavenging or exhaust timing, and a collection of metal parts starts behaving like an entirely different machine.
That is why motorcycles—especially simple two-stroke dirt bikes—make so much sense to me. There is very little decoration between the rider and the purpose of the machine. They are light, direct and mechanically honest. Complexity still exists, but most of it has a job.
I enjoy the opposite end of that spectrum too: seeing how manufacturers such as Ducati use sophisticated valvetrain and engine design to solve very specific problems. The interesting part is not whether simple or complicated is automatically better. It is whether the complexity produces something worthwhile.
That same curiosity is why channels such as FortNine and SuperfastMatt are so enjoyable to me. The entertainment is the project, but the real hook is understanding why a mechanical decision changes the whole system.
RC, drones & flight
RC cars and drones are almost perfect engineering laboratories because the feedback loop is immediate. Change gearing, motor KV, battery voltage, weight distribution, suspension setup or ESC behavior and you can feel the result minutes later. The scale is small. The systems thinking is not.
Drones add another layer: radio links, PID control, rates, filtering, propellers, motor characteristics, center of gravity and software all have to cooperate well enough that the aircraft feels predictable instead of theoretical.
That is a big part of why I enjoy people like Joshua Bardwell. There is always another nerd knob to turn, but the useful question is what that knob actually changes and whether the aircraft becomes better because of it.
I like hobbies where learning is attached to a physical result. The car accelerates differently. The drone tracks better. The motor runs cooler. The explanation becomes something you can actually experience.
Technology
Technology is another version of the same habit. I like understanding what sits underneath an abstraction, why a system behaves the way it does, and where a clever solution becomes unnecessary complexity.
Software, automation, AI, hardware and connected systems are interesting when they make a difficult thing simpler or create useful leverage. New is not automatically better, and complicated is not automatically impressive.
The best technology usually disappears into the result: it solves the problem without becoming a new hobby for everyone who has to use it.
Making & home
Home projects scratch a different version of the same itch. There is a particular satisfaction in starting with something that looks wrong, works poorly or simply was never finished properly, understanding the constraints, and ending with a physical thing that is measurably better.
I tend to like design that has form and function without accumulating features for their own sake. A light should look like it belongs on the house. A piece of trim should solve the transition cleanly. A repair should improve the underlying problem instead of merely hiding it long enough for somebody else to inherit it.
The physical nature matters too. Technology work can disappear into tickets, meetings and software releases. With a house project, the before and after are standing in front of you. The progress is tangible.
I suspect that is also why mechanical work is satisfying. There is something healthy about solving a problem with your hands and then being able to point at the result.
Systems & leadership
The same thinking eventually expands from machines into organizations. I am interested in the Toyota Way, Agile, continuous improvement and good leadership less as collections of rules and more as attempts to understand living systems.
A team has inputs, constraints, feedback loops, incentives, bottlenecks, habits and failure modes just like a technical system does. The difficult part is that the components are people, which means the system changes when you try to measure it.
I like approaches that help people see the whole flow of work and make better decisions locally. Retrospectives, visible work, swarming, standardization, experimentation and continuous improvement are valuable when they improve the system. They become bureaucracy when following the mechanism becomes more important than understanding why it exists.
A methodology followed mechanically becomes bureaucracy. Understood as a system, it can become culture.
Leadership is interesting to me for the same reason. The goal is not to personally make every decision. It is to build an environment where people understand enough of the system to make good decisions without needing permission for every useful thought.
Quality & philosophy
Somewhere between motorcycles, craftsmanship, work and systems thinking sits a larger question: what actually makes something good?
That is one reason ideas from Greek philosophy and Zen and the Art of Motorcycle Maintenance resonate with me. Quality is difficult to reduce to a checklist. You recognize it in a machine that feels right, a repair that was done properly, a team that functions well, a relationship that has been cared for, or a life that feels aligned with what somebody says matters to them.
I keep coming back to the distinction between more and better. More horsepower is not always a better motorcycle. More features are not always a better product. More process is not always a better organization. More money is not automatically a better life if obtaining it consumes the parts of life that made the money useful.
I think a meaningful life is probably much closer to a quality life: doing work with care, understanding what matters, maintaining good relationships and having enough agency to spend time on things that feel worth doing.
Family
Family is where all of the abstract talk about priorities becomes much less abstract.
One of the things I care about most is building relationships that still feel close long after children are old enough that they no longer have to be around. I want home to remain somewhere they want to come back to, not because of obligation, but because the relationships built there were worth keeping.
That requires presence more than optimization. Shared projects, conversations, ordinary time together, showing up consistently and letting people know they matter are not things that can be deferred to a future sprint.
It is easy to say family comes first while allowing work, projects and responsibilities to consume every unclaimed hour. I do not always get that balance right. The value is in continuing to notice the difference between what feels urgent and what will still matter years from now.
Possibilities
Real estate, relocation, rentals, small business ideas and other possibilities tend to get investigated deeply even when most of them never become commitments. I enjoy understanding the economics, geography, tradeoffs and second-order effects before deciding whether an idea deserves anything more than a spreadsheet.
I do not think every possibility needs to become a goal. Sometimes understanding why an idea is wrong is useful progress. Occasionally one survives the investigation.
LohTech exists partly so that when one does, there is already somewhere for it to go.
Different interests. Same recurring question: how do the parts come together, and is the result actually better?