before software,
i learned to look closely.

my route into software wasn’t particularly linear. i originally trained and worked in clinical science, where careful observation, evidence, and precision were part of doing the job properly.

that experience still shapes the way i think about software. systems meet real people and real constraints, so correctness on paper is only the beginning. reliability, verification, and understandable failure matter just as much.

i started learning programming because i was curious about how systems worked beneath the surface. that curiosity gradually became work in qa automation, where i learned to look at software from both directions: how it is built and how it breaks.

today, my work sits mostly around backend systems, apis, data workflows, automation, infrastructure, system reliability, and product engineering. i like taking something unclear, understanding its moving parts, and making it more dependable.

the tools and contexts change, but the habit is fairly consistent: observe, understand, verify, build.