Most of what I build answers the same question: where is it now? Six systems so far. The list isn't the point — the question is.
The card above isn't a picture of my work. It's generated from it, at build time, from the same collection me.kariem.dev renders: publish a seventh system and it grows a seventh lane; change a status and its dot changes fill. A number with no case study behind it can't appear on either.
83 public repos, 23 stars, 26 forks of other people's code. Most of my work
ships to clients, not to a package registry — the open repos are the ones I
chose to open. Stars measure reach; 5M req/mo measures load. And 2019-me
learned in public, so he's still up there.
| Instead of… | You get… |
|---|---|
| An API you wrap yourself, then babysit | Geolocation serving 5M requests a month to 50+ clients — four rewrites deep, live since 2023 |
| Four tools glued together by spreadsheets | One organism — storefront, ERP, ops hub, MCP server — bound by a single identity key, the customer's phone number |
| Agents that re-guess your conventions every session | Standing law they read before acting, and servers that let them drive real systems instead of describing them |
Evidence before opinion. If I haven't run it, I say so. Correction beats consistency — I'd rather be told I'm wrong early than be agreed with all the way to production.