✳flâneur — a map of the web's best reading

Infrastructure Gravity & Domain Engineering | Jack Danger

jackdanger.com · 3,926 words · saved by 1 readers

Each company draws its own line between Product Engineering and Platform/Infrastructure/DevOps but the difference between them is clear: Product Engineering is “stuff the whole company wants” (making features) and the other is “stuff the engineers say we have to do, I guess”. I’ve worked both above and below this divide and several times now I’ve led the entire span of engineering, from feature development down to whatever you call the bottom layer. I think I know why that bottom layer has so many1 names: It’s actually two separate things. Both are invisible outside Engineering but they require radically different architectures, leadership, and investment models. The Product function peers down into the technical stack like a person in a boat, trying to see the depths. There’s a limit to our perception from the surface. To see further we must plunge into the water ourself. Everything visible when looking at the UX — the surface of the tech stack — is considered “Product Engineering”. B

Table of Contents "Unique to this company, shared between features" How the middle atrophies Infrastructure Gravity Feature Lift The Gap - A space for Domain Engineering A Financial Model of Domain Engineering The following is an excerpt from Executive Engineering . "You become responsible, forever, for what you have tamed." – Antoine de Saint-Exupéry, in The Little Prince Each company draws its own line between Product Engineering and Platform/Infrastructure/DevOps but the difference between them is clear: Product Engineering is "stuff the whole company wants" (making features) and the other

Explore this link on the map →

saved by

related reading