Part 1: Khartoum, Adaptation Before Engineering

The Traits Came First

Before I had language for any of it, there were just patterns. When something didn't work, I wanted to understand why before I did anything else. When a situation changed, I adjusted without much friction. I didn't think of these as skills — they were just how I moved through things.

Looking back, the adjustment instinct and the diagnostic reflex were there early. The environment I grew up in didn't create them, but it made them load-bearing. It gave them constant exercise. That's the version of the story I want to tell first — not what happened around me, but what was already in me when it started.

Sudan Made Those Traits Necessary

Khartoum was where I grew up, and the baseline there was unpredictable. Power went out. Water supply wasn't reliable. Connectivity was inconsistent. This wasn't unusual — it was just the condition. You planned around it, or you didn't get things done.

Our home ran workarounds for all of it. Backup power, stored water, fuel reserves, offline systems when the network was down. Each gap got addressed when it showed up. You plug one hole and something else surfaces. That cycle doesn't end — it just becomes the operating rhythm.

None of this felt dramatic from the inside. It was just maintenance. But the pattern it reinforced was specific: don't react before you understand it, don't assume the system will hold, build the fallback before you need it.

My Parents Set The Frame

My father is a practicing surgeon. He studied medicine in the UK, and when he came back to Sudan, he came back with a specific mission: raise healthcare standards there, and extend that work across Africa. Not as an abstract goal — as an actual operating plan.

To do that, he needed more than clinical work. He started sourcing pharmaceutical products, medical equipment, and instruments from abroad and bringing them into Sudan and across the continent. He got involved in designing and helping build hospitals in the region. He was operating at every layer simultaneously — treating patients, running a business, contributing to infrastructure. That wasn't unusual to me growing up because it was just what I saw. Work wasn't a single thing you did. It was a system you built around a purpose.

My mother is a teacher and professor. Both of them trained in the UK. Both of them chose to come back. I've thought about that choice a lot over the years — it wasn't the obvious move, and it wasn't framed as sacrifice either. They just had somewhere specific they wanted to build, and they went and built it.

What I absorbed from watching my father in particular was the multi-domain picture. He wasn't compartmentalizing — clinical, commercial, infrastructure were all expressions of the same project. That's a particular way of thinking about what work is, and I didn't realize how much it shaped me until I started watching how other people think about it.

What It Built In Me

Put all of that together and what you get is a particular way of seeing systems. Where are the failure points. What happens when one layer goes down. How do you keep the whole thing running when conditions shift. I wasn't calling it anything at the time — it was just how the environment trained me to think.

I came to biomedical engineering through that lens before I ever set foot in a lecture hall. The formal language came later. The instincts were already there.

For broader context on where all of this was happening, see my notes on Sudan.