Interfaces people enjoy using, backends that hold up in production, and the tooling in between. Some of it ships with a team, some of it stays private, and some of it I give away. All of it gets the same standard: clear behaviour, honest errors, and nothing left for the next person to guess.
TypeScript is my common language across web, backend, mobile and desktop. When a tool belongs on my Mac, I write it in Swift; on Linux, in Rust. I am completing an M.S. in Computer Engineering at the Lebanese International University, and going deeper into AI and machine learning.
I tell computers what to do, and sometimes they listen.
TypeScript end to end, Swift when it belongs on the Mac, and whatever the problem actually needs underneath.
features
01 Make the wrong thing unrepresentable.
If a bug can be prevented by the schema, the type system or the database, it should never reach a code review.
02 Boring infrastructure, sharp edges.
Pick proven tools for the foundation so the time goes into the details people actually touch.
03 Legible software.
Tools should explain themselves: why a process would not die, why a Mac is awake, why a token is unsafe.
04 Ship, then keep it working.
CI, security scanning and invariants you can run matter as much as the first release.
absolute maximum ratings corner radius 0 px, em dashes 0, emoji 0, unexplained errors 0. Stresses beyond these ratings may cause permanent damage to the device.
Email is the fastest way to reach me, at contact@khaledsaeed.tech. For anything that needs a conversation, book a call.
Selected work is pinned below. Everything else is printed at khaledsaeed.tech.