I got here by shipping things that had to work.

I’m a mobile engineer in Cairo, Egypt. For the last four years I’ve built Flutter applications end to end — architecture, state, backend integration, store release — mostly for products where I was the person responsible when something broke.

That shapes how I work. When you own a product from Figma file to Play Store listing, you stop optimising for how clever the code reads and start optimising for how quickly you can understand it at 11pm with a crash report open. Most of my engineering opinions come from that, not from a conference talk.

I studied Computer Science at The Future University, started with a community healthcare app as an intern, and have since worked across e-learning, e-commerce, payments, and AI-assisted productivity. The domains changed; the questions didn’t — what’s the real constraint, what breaks first, and what does the user do when it does.

Lately I’ve been writing more of it down. Partly because explaining a decision is the fastest way to find out whether it was a good one, and partly because the engineers I learned the most from were the ones who published their reasoning rather than their results.