My work, written down.My work, written down.

I am Maged, a software engineer. I don't chase what's popular, I chase problems, mine mostly. When something I use is missing a feature, half-broken, or doesn't exist yet, my instinct is to go build the version that isn't, in whatever the problem actually calls for: web, mobile, a game engine of its own, a client's stack. What I care about once I'm in the code is less the feature and more whether it survives contact with reality: the dropped connection, the rate limit, the edge case that only shows up in production. I'd rather ship something small and dependable than something big and fragile.

Writing it down is the habit that outlasted the rest. That one is on my friend Eman, who kept sending me his deep-dive posts until I started writing my own. It clicked the day I opened an old project of mine and could not remember what half the code did. Read in order, they also double as a record of how I have grown from one project to the next, not just a list of what shipped. If a project was not worth writing about, it is not here.