Writing · Nº 041065 essays
The writing
Ideas from inside the work. Explore technology, entrepreneurship, and the practice of building things that last.
21 essays found · Page 2 of 2
Clear filtersOperatingHow to Replace Your Business Tool Stack Without DowntimeReplace your business tool stack without downtime by migrating one function at a time, running parallel, and cutting over on proof. A practical playbook.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.EngineeringThe Strangler Pattern for Legacy Code, Done RightHow to replace legacy code without a rewrite. The strangler pattern lets you route new work to new code and retire the old system piece by piece, safely.EngineeringUse AI to Migrate a Framework VersionA framework version migration is AI's best-case scenario: mechanical, well-defined, and testable. Here is how to run one without breaking production.StrategyData Gravity Is the Real Lock-In, Not Your ContractVendor contracts are not what trap you. Data gravity is: the mass of data and integrations that make leaving a platform slow. Here is how to fight it.OperatingHow to Migrate Your CRM Off Spreadsheets Without Losing HistoryA practical way to migrate a CRM off spreadsheets: map your columns, keep every note and date, and import so nothing gets orphaned or duplicated.OperatingHow to Migrate From HighLevel to an Agency OSA practical order of operations to migrate from HighLevel to an agency OS: what to move first, what breaks, and how to avoid losing client history.OperatingHow to Calculate the Payback Period on a Platform MigrationA platform migration ROI is a payback period, not a gut call. Here is the math I use to decide when leaving a managed platform pays for itself.EngineeringHow to Migrate Off Managed Cloud Without DowntimeThe real runbook for moving an app off managed hosting onto infrastructure you own: database migration, DNS cutover, backups, and rollback, with the failure points named.