Writing · Nº 041065 essays
The writing
Ideas from inside the work. Explore technology, entrepreneurship, and the practice of building things that last.
26 essays found · Page 1 of 3
Clear filtersThesisWhy Shipping Speed Is a Trap and Compounding WinsOptimizing for raw shipping speed feels productive and quietly bankrupts you. Here is why a compounding foundation beats speed over any horizon that matters.StrategyIs Your Shared Foundation Paying Off? Metrics to CheckHow do you know a shared foundation is paying off? Track time-to-first-deploy, per-product maintenance, and foundation reuse. Here are the metrics that prove it compounds.EngineeringOne Billing Engine Under Every Product You RunA shared billing engine across products means one place for subscriptions, invoices, and payment failures. Here is why per-product billing is a mistake in a portfolio.StrategyWhere to Let Portfolio Apps Diverge From the FoundationA shared foundation should not standardize everything. Knowing where to let portfolio apps diverge is what keeps the foundation useful instead of a straitjacket.EngineeringArchitecture Decision Records Are a Compounding AssetThe cheapest knowledge asset you can build is a log of why you chose what you chose. Here is why architecture decision records compound across a whole portfolio.StrategyThe Hidden Cost of Not Having a Shared FoundationThe cost of not having a shared foundation is invisible until it isn't. Divergence, repeated work, and per-product maintenance quietly cap how many products you can run.ThesisIs Your Shared Foundation a Single Point of Failure?A shared foundation means one bug can break every app at once. Here is how to get the compounding upside without turning the foundation into a portfolio-wide fault line.OperatingSelf-Serve Docs Make an Internal Platform ScaleAn internal platform without docs is a bottleneck, even solo. Self-serve documentation for your shared foundation is how the platform scales past the person who built it.OperatingOne Runbook for Twenty Apps: Amortized OpsOne runbook for twenty apps is how a solo operator survives. When every product runs on the same foundation, ops is written once and amortized across the whole portfolio.EngineeringHow to Move an Existing App Onto Your Shared FoundationBuilding a shared foundation is easy on new apps. Retrofitting an old one is the hard part. Here is how to migrate a live app onto the foundation without a rewrite.EngineeringHow to Test a Shared Foundation Before It Breaks AppsTesting a shared foundation is different from testing one app. A change touches every product. Here is how to test the foundation so one edit does not break twenty apps.StrategyOne Design System Across Many Brands, Without Cloning ThemYou can run one design system under products with different brands. The secret is theming the semantic layer, not the components. Here is how to keep them distinct.