Writing · Nº 041065 essays
The writing
Ideas from inside the work. Explore technology, entrepreneurship, and the practice of building things that last.
9 essays found · Page 1 of 1
Clear filtersEngineeringUse Repo Intelligence to Split a MonolithSplitting a monolith by guesswork creates a distributed mess. Learn how repo intelligence finds the real seams so you decompose along boundaries that exist.EngineeringWrite Characterization Tests Before You RefactorYou cannot safely refactor untested legacy code. Characterization tests capture what the code actually does so you can change it without breaking behavior.EngineeringHow to Estimate Refactor Effort Before You StartRefactor estimates are usually guesses. Learn how to estimate refactor effort from repo signals like coupling, churn, and test coverage instead of gut feel.EngineeringHow to Find and Remove Dead Code SafelyDead code inflates your repo, hides risk, and slows everyone down. Learn how to find dead code with confidence and remove it without breaking production.EngineeringThe Coupling Metrics That Predict Real PainCoupling is the maintainability metric that best predicts where changes break things. Learn afferent and efferent coupling and how to read them in your repo.EngineeringWhen Not to Refactor Legacy CodeNot all legacy code should be touched. Learn when refactoring legacy code is a waste of budget and when leaving ugly, stable code alone is the right call.EngineeringSecurity Debt vs Technical Debt: Not the SameSecurity debt and technical debt look alike but behave differently. Learn how to tell them apart, why they need separate budgets, and how to prioritize each.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.EngineeringChurn vs Complexity: Find Your Real HotspotsComplex code is only dangerous when it changes. Cross churn against complexity to find the hotspots in your repo that actually deserve a refactor first.