About Me
I don't finish things halfway. If I take something on — a system, a problem, a stupid edge case at 2am — I see it through until it's right, not until it's good enough.
I got into engineering because I wanted to understand how things actually work, not just that they do. That curiosity hasn't been selective. I've debugged telemetry on a nanosat, taught a model to read satellite imagery, and spent an unreasonable amount of time making sure a permission system couldn't be gamed by its own admin. The problems don't have to be related. They just have to be real.
I build alone a lot. That means I've had to be the one who catches the race condition, writes the migration script, questions the schema at 3am, and cleans up the mess I made last week. I don't love every part of that — but I've stopped flinching at any of it.
I'm not sure where I'm headed exactly. But I know what kind of engineer I want to be: the kind who owns the work, asks the uncomfortable questions early, and never ships something they don't understand.
Still figuring out the rest.