Mo Jahani — Software Engineer & Scalable Solution Architect on Mo Jahani

Designing for millions: lessons from scaling a real-time API

Thu, 28 May 2026 00:00:00 +0000

The morning it happened, I was making coffee. A small tool I’d built to broadcast live scores had been picked up by a popular account overnight, and by 9 a.m. it was fielding more traffic in a minute than it had seen in its entire life. Nothing was technically down; it was just slow in a way that felt personal. That day taught me more about systems than a year of reading ever had.

Why I stopped fearing the database and learned to love SQL

Tue, 14 Apr 2026 00:00:00 +0000

For most of my twenties I thought of the database as plumbing. Something that lived behind an ORM, spoke a language I half-remembered from a university course, and was best left undisturbed. I wrote User.where(active: true) and whatever happened next was not, in any meaningful sense, my problem.

Embedded to web: what microcontrollers taught me about performance

Mon, 30 Mar 2026 00:00:00 +0000

My first serious programming job had a hard limit printed on the datasheet: 8 KB of RAM, 64 KB of flash. Not “8 KB before it gets slow.” 8 KB before the device stops working and a technician drives out to a site to find out why.

A pragmatic guide to Docker for small teams

Wed, 18 Feb 2026 00:00:00 +0000

Most Docker advice is written for organisations with a platform team, a service mesh, and a dedicated on-call rotation. If you’re four people shipping a product, that advice will cost you a month and give you back a system nobody fully understands.

ClickHouse vs. Postgres for analytics: a field report

Thu, 22 Jan 2026 00:00:00 +0000

We had a billion rows of event data and a dashboard that had stopped being usable. The obvious move was to put the analytics somewhere purpose-built. The less obvious question was whether we needed to at all.

Clean code is a feature, not a luxury

Tue, 09 Dec 2025 00:00:00 +0000

“We’ll clean it up later” is the most expensive sentence in software, and it’s expensive in a way that never shows up on the ticket that caused it.

I’ve stopped arguing for clean code on aesthetic grounds. Nobody wins that argument, and honestly nobody should: a beautiful codebase that ships nothing is worth less than an ugly one that pays salaries. The argument that works is narrower and harder to dismiss: readable code is faster to repair under pressure, and every system eventually needs repairing under pressure.

Let's build something worth shipping.

Mon, 01 Jan 0001 00:00:00 +0000

Mo Jahani

Mon, 01 Jan 0001 00:00:00 +0000

Hi, I’m Mo. I enjoy taking ideas and turning them into work that makes a meaningful impact.

From embedded devices to web apps serving millions of users, my focus is finding the point where technology and business goals meet. I care about building reliable systems, delivering genuine value, and keeping clients happy, all while pushing performance as far as it will go.