What keeps me interested
What keeps me interested in engineering isn't just building — it's understanding how things hold up over time. I work as a software engineer focused on clean design, practical decisions, and systems I can stand behind, alongside a small number of freelance and consulting projects on the side.
Over the last few years my priorities have shifted from speed toward clarity and consistency — thinking less about the immediate task and more about how things evolve for users, teams, and the product itself.
I come from a family full of doctors, so the expected path ran through biology. I chose Electronics & Communication Engineering instead — adjacent enough to feel familiar, and still my own decision. In my first year I wrote my first real line of code for the web, and that turned out to be the thing that held my attention.
I taught myself the basics, then kept going — freelance projects, client work across a handful of industries, and a long stretch of building things nobody asked for, just to understand how they worked. A lot of what I know came from maintaining my own earlier decisions long enough to learn from them.
The electronics side never fully went away. I spent time building interfaces for a neural network running on PYNQ Z-series hardware, and that work became an IEEE paper on signal analysis. Signal processing and hardware still shape what I find interesting — they just aren't what I do every day.
