About
I'm Hazem Mohamed. I've spent a long career building and running software; this is where I write down the parts worth keeping.
I've shipped and operated software long enough to watch clever architectures go bad and plain ones last a decade. Somewhere along the way, the interesting problems stopped being technical and became human: judgment, tradeoffs, trust.
Tiplite is the notebook I wish I'd kept earlier: essays on architecture tradeoffs, code review without theater, and the quiet habits that keep systems — and teams — durable.
If a piece is useful, take it. If it's wrong, say so. I'm optimizing for clearer thinking, not reach.