About Mimar

A mimar is a master builder. The word is the same in Arabic and Turkish, and it carries the Mimar Sinan lineage: the person responsible for the thing standing up, not for the drawing of it.

I started as a civil engineer. My first mental model was the load path: every force has to reach the ground, and it will find its own way there whether or not you drew that way. Then I spent a decade building software, in game engines, edge computing and machine learning systems. That gave me a second model: systems fail at their interfaces, not their components.

Today I work where the two meet, on delivery intelligence for AI data center construction. The pattern the record shows on every complex build, from Crossrail to nuclear megaprojects, is this: most delay is not a planning failure, it is a distribution failure. The information existed. It just did not cross a boundary in time.

How I got here

My father took me onto construction sites in Cairo before I was old enough to be useful on one. Growing up there, the reference class for a large project is not an office tower. It is the pyramids, which are the first megaprojects we have any record of, and which are still the local unit of measurement for ambition.

History's first named engineer was Egyptian. Imhotep is credited by name on the Step Pyramid, which is unusual, because the pharaohs generally got the monuments. The builder delivered them. That distinction is more or less the subject of this publication.

I studied civil engineering at Ain Shams University, structural. Then software took a decade of my life, which I do not regret, because it is the half of the education that construction is currently missing. Now I work on American data centers, the largest privately funded build program of this decade. Someday I would like to do this work back home.

What gets published here

Two formats, for now.

Essays take a megaproject with a deep public record, usually one that published its own lessons, and read it for what transfers to data center delivery. Long form, evidence first.

Reconciliations are the short format. Two public documents describe the same project and disagree. The table is the piece. The disagreement is the story.

Everything here is built from public documents and synthetic examples. No employer material appears on this site, in any form. Where I use a framework that is not mine, it is credited to the people who built it.

The RSS feed is the only way to subscribe. There is no list, no tracker and no cookie banner.