Most of the systems I am proud of are built from boring parts. The interesting engineering was never the technology choice. It was the failure handling.
The parts list
Postgres. A queue. A cache with an invalidation rule someone actually wrote down. Services small enough that one person can hold one in their head.
None of that would impress anyone on a slide. All of it is well understood, well documented, and has failure modes other people have already found for you.
Where the real work is
What made those systems good was what they did when things went wrong: retries that do not duplicate work, timeouts that are actually set, shutdowns that drain cleanly, and someone deciding up front when data is allowed to be stale.
Nobody puts that on a slide.
Takeaways
- Boring, proven technology lets you spend your effort elsewhere.
- Write down cache invalidation rules.
- Keep services small enough for one person to understand.
- The engineering that matters most is failure handling.
Building something like this?
I'm Ahmed Mamdouh, a senior full-stack & AI engineer. I reply within one working day.
MCP went stateless, and that matters
The July MCP revision went stateless with OAuth 2.0 and OpenID Connect, so MCP servers can now run behind load balancers and serverless.
Claude output is now watermarked
Claude output now carries watermarks and signed provenance by default; tell your users, and never treat a missing watermark as proof.
Green flags that someone is genuinely senior
A genuinely senior engineer volunteers a decision they got wrong and what it taught them, and asks about on-call before tech stack.