Writing · Nº 041065 essays
The writing
Ideas from inside the work. Explore technology, entrepreneurship, and the practice of building things that last.
16 essays found · Page 1 of 2
Clear filtersEngineeringCode Review Misses Architectural DecayCode review catches line-level bugs but misses architectural decay entirely. Learn why your repo rots one approved pull request at a time and how to catch it.EngineeringStatic Analysis vs Repo Intelligence: The GapStatic analysis finds bugs in files. Repo intelligence finds risk across the whole repo and its history. Learn the difference and why you need both.EngineeringLockfiles and Supply Chain Integrity, ExplainedYour lockfile is the last line of defense for supply chain integrity. Learn what it protects, how it fails, and how to verify what actually ships in your build.EngineeringUse 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.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 the Bus Factor in Your CodebaseBus factor measures how much of your repo only one person understands. Learn to find knowledge concentration risk in code and spread it before it hurts.EngineeringWhich CVE Alerts Actually Matter in Your RepoMost CVE alerts in your dependency scanner are noise. Learn how reachability and context decide which vulnerability alerts are real risk worth fixing now.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.EngineeringAutomated Scan vs Expert Review for Code Due DiligenceShould code due diligence be an automated scan or a human expert review? The answer is both, in order. Here is how to sequence automated scan vs expert review.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.