Mohamed Aldulaimi — Collected pages
a brief about me, some of the work I’ve done, and field notes on things worth writing down
With JavaScript enabled this site is a book you can leaf through; here is the full text.
About me
My name is Mohamed, and this book is my website. I'm a software engineer who likes building things that feel a little more considered than they strictly need to — which is probably how you ended up holding a book instead of scrolling a feed.
These days I build products at Signit, where documents get signed and promises get kept. Before that, a winding road of projects, prototypes, and the occasional production incident that taught me more than any tutorial ever did.
I keep this book the way some people keep a notebook: a short brief about me, a record of work I'm proud of, and field notes — small essays on whatever seems worth writing down properly.
What am I about? Mostly: software engineering and trying my best to be a great husband and father.
Off the keyboard you'll find me working out, or reading — slowly, on paper — which is the quiet joke of this entire website.
Selected work
Every project in this chapter is one I'd happily explain at a whiteboard for an hour. That's the bar for inclusion — not size, not novelty, just whether the problem was real and the solution held up.
Signit — building the product that turns signatures into software: the flows people trust their contracts to, and the machinery underneath that keeps that trust cheap to give. War stories and architecture sketches to follow.
Salalem — provided the needed education and meeting compliance goals for employees in many different sectors, most prominantly, banks. I started as a software engineer and 3 years later became a tech lead, worked there for 1 and a half years before moving on to Signit.
Quiz Buddy - gave students the ability to enter a mock exam as many times as needed before their real one by simply uploading their exam material to the app. Over 700 students used this app during the university exams periods.
The last five percent
There's a point in every project where the thing works. The demo passes, the tests are green, everyone is ready to move on. What's left is the last five percent: the empty state nobody designed, the error message written at midnight, the animation that's 80 milliseconds too slow to feel intentional.
The last five percent is invisible in a feature list and unmistakable in the hand. It's the difference between a door that closes and a door that closes well. Users can't name it, but they feel it instantly, and they trust the software more without knowing why.
It is also, minute for minute, the most expensive part of the work — which is exactly why it's rare, and exactly why it's worth doing. Anyone can ship the first ninety-five percent. The last five is where you sign your name.
This book is my attempt to practice what that means: nobody needed the drop caps. That's the point.