Principal Engineer · 16+ years

Helping senior engineers think and design like architects.

I write about system design, mentor engineers moving toward staff and principal, and teach what I've learned the hard way.

Or go deeper: the live cohort
Live cohorts on Maven500+ articlesThe Breakpoint podcast

What engineers say

29+ engineers and colleagues, sharing what changed after we worked together.

It has been a pleasure working with Ehsan. He is a dedicated, self-motivated and knowledgeable software engineer. He always embraces new challenges at work. He has a positive attitude and desire to produce quality work that serves him well. He would be a valuable team member of any software team.
Anitha P.
QA Automation Engineer at Sportsbet
Ehsan consistently delivers the best in company projects on time and to high standards. I have always admired his ability to stay calm and perform under pressure. He is a great asset to the team both on a professional and personal level. I would not hesitate to recommend Ehsan.
Payam Mousavi, Software Developer at Thoughtworks | AWS Certified
The session was amazing and so informative covering a lot of topics like reviewing linked profile, CV and GitHub profile. Thank you so much for your time, Gaz.
Ahmed Abdelhamed, Software Engineer
Read all 29+ testimonials →

More ways to learn

Latest writing

View all →
Containers vs Cloudflare Computer: There Is Not Enough Compute for One Box Per Agent
Artificial Intelligence

Containers vs Cloudflare Computer: There Is Not Enough Compute for One Box Per Agent

Nearly every agent framework decided that one agent means one container. Cloudflare says there are not enough computers on earth for that to work, and has flipped it around: the agent lives in a tiny sandbox with a filesystem that stays behind, and a container is only borrowed when Linux is truly needed. Here is the argument in plain words, why Cloudflare made it, and where I would use it.

Graph Engineering: Every Edge You Draw Takes a Decision Away From the Model
Artificial Intelligence

Graph Engineering: Every Edge You Draw Takes a Decision Away From the Model

Agent graphs are state machines with a new name on them. The engineering question is not what a node is, it is which routing decisions you take away from the model and which you leave to it. The rule I apply: only draw edges for decisions you can make better in advance than the model can at runtime.

When Your Data Is Really a Graph: Write the Recursive Query First
System Design

When Your Data Is Really a Graph: Write the Recursive Query First

Some questions cannot be answered by adding one more join, because the number of joins depends on the data rather than on the query. That is the moment your data has become a graph. Here is how to tell, what a graph actually buys you, and the two costs nobody mentions until you are already paying them.

Semantic Caching for AI Requests, Explained Simply
Artificial Intelligence

Semantic Caching for AI Requests, Explained Simply

Your users ask the same question in different words, and you pay for every one. A semantic cache answers from meaning instead of exact text. Here is how it works, in plain language, with a working version you can build in an afternoon.

The Algorithms Worth Knowing in Code Review: Cutting Big O Without Being Clever
Algorithm

The Algorithms Worth Knowing in Code Review: Cutting Big O Without Being Clever

The small set of algorithm changes that actually come up in code review, each one shown as before and after, with the Big O it removes.

TypeScript Anti-Patterns That Cost You Twice: Build Time, Runtime, and the Interview
TypeScript

TypeScript Anti-Patterns That Cost You Twice: Build Time, Runtime, and the Interview

The TypeScript patterns I keep deleting in code review, what to write instead, where the cost lands, and the interview question each one turns into.

Popular this week

What other engineers have been reading in the last seven days.

Where to start

The deep dives I'd point a senior engineer at first, grouped by topic.

All 16 topics →