How I Got Into Engineering

I got into engineering before I knew the word meant anything formal. As a kid I would sneak off to stare at the night sky and ask the kind of questions that do not help with homework but ruin your peace in a useful way. Why do patterns repeat? Why do systems hold? Why does one tiny change make the whole thing behave differently?

Later that same instinct showed up in smaller, more practical places. I remember writing a Fibonacci program in school because I wanted to see whether the pattern could be rebuilt from first principles rather than memorized. That mattered to me more than the answer itself. I liked the feeling of deriving structure.

The deeper pull came when code stopped being abstract and started touching the physical world. Building things with friends, wiring parts that should not have worked together, staying up far too late debugging what turned out to be one stupid mistake. Those were the moments that made engineering feel honest. Reality does not care about style points. It either works or it does not.

That honesty is still what keeps me here. Good engineering removes drag. It takes repetition, confusion, and fragile manual work and turns them into systems that behave well under pressure. I have ended up building automation agents, AI pipelines, developer tools, and performance-heavy systems for exactly that reason. They give time back.

The thread between all of it is simple: I like understanding how things talk to each other, where the friction hides, and what happens when you design with enough care that people no longer have to think about the machinery at all. That is how I got into engineering. Curiosity first. Then systems. Then the quiet satisfaction of making something hold.