Readable beats clever
The next person to open this file is probably you, six months from now, with no memory of writing it. I write for that person.
About
Who you would be working with
I am Mahmoud El-Aidy. I build web and Android applications, usually alone, usually from the first sketch to the deployment. I care most about the parts nobody demos: what happens on a bad connection, what the error message says, how long the third page takes.
I started because things annoyed me and I wanted them to stop. That has not really changed — most of my better work came from taking something slow and irritating and making it quick and quiet.
These days I mostly work with founders and small teams who need one person to carry a product end to end rather than three people to coordinate. That suits me. I would rather own a whole thing than a slice of one.
I am not the right choice for everything. Very large teams, heavy data science, anything needing a design department — you want someone else, and I will say so on the call rather than after the invoice.
Slow is a bug
If it drags on a mid-range Android phone on a weak connection, it is not finished. That is the device most of your users actually hold.
Dates I can keep
I would rather say six weeks and deliver in six than say three and go quiet in week four. Padding a timeline is cheaper than losing your trust.
Accessible from day one
Keyboard navigation, contrast, screen readers. Retrofitting this at the end costs more than doing it as I go, and it usually gets cut instead.
- Next.js
- React
- TypeScript
- Kotlin
- Jetpack Compose
- React Native
- Node.js
- PostgreSQL
- Prisma
- Tailwind CSS
- GSAP
- Docker
- Redis
- Figma
Still reading?
Then we should probably talk. Thirty minutes, free, no slide deck. Worst case you leave with a second opinion.