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 2 of 3
Clear filtersEngineeringHow to Spin Up a New App in a Day on a Shared FoundationSpinning up a new app in a day is the real test of a shared foundation. If a new product takes a week to bootstrap, your foundation is not compounding yet.StrategyWhen to Fork a Product Out of the Shared FoundationWhen should a product leave the shared foundation? When its needs diverge so far that the foundation costs more than it saves. Here are the signals to fork out.EngineeringAn Internal CLI Is the Cheapest Compounding Tool You Can BuildThe highest-leverage internal tool is a CLI that scaffolds every new app the same way. Here is why an internal CLI compounds harder than any shared library.EngineeringBuild an Internal Framework or Use Off the Shelf?Should you build an internal framework or use off-the-shelf tools for a portfolio foundation? The answer is thin glue over standard tools, not a homegrown framework.EngineeringOne Identity Layer Across Every Product You RunA single identity layer across products means one place for auth, sessions, and users. Here is why a shared identity layer beats per-product auth in a portfolio.OperatingWho Should Own Your Shared Component LibraryA shared component library with no owner rots into a dumping ground. Here is who should own it, what ownership means, and how to keep it from becoming a bottleneck.EngineeringA Shared UI Component Library Across ProductsA shared UI component library across products cuts build time and keeps a portfolio coherent. Here is what to share, what to leave per-product, and how to avoid rigidity.OperatingWhy Playbooks Compound Faster Than Shared CodeShared code is stack-bound and fragile. A written playbook travels across every product and every tool. Here is why playbooks compound faster than a shared library.EngineeringHow to Roll Out Breaking Changes Across a PortfolioRolling out breaking changes across a portfolio of products means expand, migrate, contract. Never break twenty apps at once. Here is the safe sequence I use.StrategyWho Pays for the Internal Platform in a PortfolioWho pays for the internal platform when it serves twenty products? The first product carries it, and every product after that pays almost nothing. Here is the math.EngineeringCopy-Paste vs a Shared Dependency: When Each WinsNot every repeated piece of code belongs in a shared dependency. Here is how to decide between copy-paste and a shared library so your foundation compounds.EngineeringHow to Version a Shared Foundation Without Breaking AppsVersioning a shared foundation across many products means additive changes, deprecation windows, and pinned versions. Here is how to upgrade without breaking apps.