North Star

Most early engineering goals are immediate: learn a new language, ship a feature without breaking staging, understand why a Docker container won't bind to a local port. Those milestones are necessary. They give you the reps needed to stop worrying about basic syntax so you can start paying attention to how systems actually behave.

But when I look past the immediate projects in front of me, the long-term ambition is different. I want to eventually become technically capable enough to identify and bridge a genuine gap, or build a foundation that other engineers can build on.

I think about the pieces of technology that quietly anchor modern computing—how Linux became foundational infrastructure, or how the Transformer architecture shifted the trajectory of machine learning. The goal isn't to imitate those specific artifacts. I don't pretend I'm going to 'build the next Linux' or 'invent the next Transformer.' That kind of grandstanding misses the point. The ambition is about the caliber of capability required to see a fundamental problem clearly and solve it at the root.

Along the way, building smaller foundations from first principles—whether that means writing a simplified Git clone, compiling a toy operating system kernel, training a miniature transformer from raw matrix math, or building a custom runtime—serves as invaluable practice. Those aren't the destination; they are stepping stones that force an honest understanding of how machines and software actually work underneath layer upon layer of abstractions.

I have no illusions about the timeline or the certainty of getting there. It could take five years, twenty years, or take a shape I cannot anticipate right now. It might turn out that I never build anything widely foundational at all. That uncertainty isn't something I feel the need to resolve or hide behind a confident career pitch.

What matters is the direction of the work. For now, I have some things to learn.