IF MY CODE WERE A PODA-PODA, THE BACK WOULD SAY:
- Optimize for constraints
- Clarity over cleverness
- Systems over features
On building
-
Ship early.
Learn from real users, not assumptions. The first version exists to be corrected.
-
Complexity is a liability.
Kill it on sight. Every moving part is something that breaks on a Friday night.
-
Performance over trend.
A fast, plain thing beats a slow, fashionable one. Always.
On emerging markets
-
3G is not an edge case.
It's the baseline. Design for the connection most people actually have.
-
Payment failure is not a bug.
It's a business problem. Treat retries, reconciliation and refunds as product, not plumbing.
-
Regulatory friction is a moat.
If you learn to navigate it. Most people won't, and that's the point.
On learning
-
Read primary sources.
Summaries are lossy. Go to the spec, the paper, the law.
-
Build the thing to understand the thing.
Reading about a system and running one are different kinds of knowing.
-
Teach it.
Writing forces precision. That's most of why this notebook exists.
— Umaru
pass me a note?
One field note a month, straight to your inbox. No growth hacks.