Mohamed Halawa

Every system has a history — a chain of trade-offs someone weighed to get it where it is. The code shows what got built; the reasoning behind it usually goes undocumented, then forgotten. That reasoning is what I write down here.

I'm a backend engineer at Coolblue, building systems where correctness isn't optional. Most of what I publish started as something I had to understand deeply before I could trust it: a design I argued about, a trade-off I kept second-guessing, a "why is it this way" that took real digging.

No fixed topic — distributed systems, architecture, whatever I'm reasoning through. If that's your thing, the posts are a good place to start. Off the keyboard I shoot street photography — the same habit of looking for the pattern, on Instagram.