Writing · Nº 041065 essays
The writing
Ideas from inside the work. Explore technology, entrepreneurship, and the practice of building things that last.
12 essays found · Page 1 of 1
Clear filtersEngineeringRun Repo Intelligence Before You RefactorRefactoring without repo intelligence is guessing. Here is how to map churn, coupling, and blast radius before you refactor so you fix the right code safely.EngineeringHow to Prioritize Which Tech Debt to Fix FirstNot all tech debt is worth fixing. Here is how to prioritize which technical debt to pay down first using interest, blast radius, and your actual roadmap.OperatingDo You Actually Need a Code Audit?Your team knows the codebase, so why run a code audit? Here is when a repo audit earns its cost, when it does not, and the objection that it is a waste.AIHow to Score AI-Generated Code Before You Ship ItAI writes code fast but you still own it. Here is how to score AI-generated code for quality, coupling, and real test signal before it reaches production.ThesisTech Debt Is a Balance Sheet, Not a ConfessionTechnical debt is not a moral failing. It is a balance sheet you should manage on purpose. Here is how to treat tech debt as leverage instead of shame.EngineeringWhy Code Metrics Mislead You About QualityLine count and complexity scores feel objective but mislead you about code quality. Here is why raw code metrics lie and what to measure in a repo instead.StrategyA Repo Due Diligence Checklist Before You AcquireBefore you buy a company or codebase, run this repo due diligence checklist. Nine checks that reveal tech debt, key-person risk, and rewrite traps early.EngineeringCommon Mistakes When Reading a Repo AuditA repo audit is only as good as how you read it. Here are the common mistakes that turn a useful code audit into false comfort or panic, and how to avoid them.EngineeringCode Quality Score vs Test Coverage: What to TrustCode quality score vs test coverage: they measure different risks. Here is what each one actually tells you and why coverage alone will lie to your face.EngineeringHow to Measure Technical Debt in a RepoYou cannot pay down what you cannot see. Here is how I measure technical debt in a real repo using churn, coupling, and change cost instead of vibes.EngineeringHow to Audit a Codebase You InheritedInherited a codebase you did not write? Here is the exact order I audit an unfamiliar repo to find risk fast, before I commit to owning or changing it.EngineeringWhat a Code Quality Score Actually MeasuresA code quality score is not one number. Here is what it should measure, what it should ignore, and how to read one without fooling yourself into false comfort.