About CodeSmellCost.com
CodeSmellCost.com is the cost-attached translation of Martin Fowler's 22-smell catalog into language engineering leaders can take to a CFO. Every smell on the site gets a dollar range, a detection recipe, and a refactoring pattern. The calculator behind the home page is the full math, open and reproducible, with CSV export.
The site is published by Digital Signet. It is independent, vendor-neutral, and not a lead-generation funnel for a tooling vendor or consultancy.
Fowler's Refactoring (Addison-Wesley, 1999; 2nd ed. 2018, with the JavaScript examples) defines the vocabulary every engineering team uses for code quality. The book describes 22 smells, gives each one a refactoring pattern, and explains the mechanism. What it does not do is attach a dollar figure. The book pre-dates the CFO conversation.
The vendor glossaries (SonarSource's SonarQube docs, JetBrains' refactoring catalog, refactoring.guru, CodeAnt) describe smells in plain prose but never quote a number. The peer-reviewed empirical literature (Bavota et al. ICSE 2015, Bird et al. FSE 2011, Khomh et al. 2012, Rahman 2025) reports correlations and effect sizes but is not aimed at engineering leaders making spending decisions. The Stripe Developer Coefficient Report (2018, updated 2023) gives the headline macro number ($85 billion per year in lost developer productivity globally) but does not break it down by smell.
The gap is the translation layer. CodeSmellCost.com is that layer: Fowler's catalog, dollar-attached, cited to peer-reviewed research, organised for the executive committee.
Oliver Wakefield-Smith runs Digital Signet, an independent consultancy that builds AI systems and operates a portfolio of editorial reference sites in the engineering, FinOps, and tech-debt space. CodeSmellCost.com is one of those sites. Oliver writes the analysis, runs the cost model, and signs the corrections.
Sister sites in the same editorial family:
- featurebloat.com - The product-management mirror: same argument, from the PM's side of the table.
- techdebtcalculator.com - Calculator-first sister site on the broader 'technical debt' surface.
- incidentcost.com - Production incident cost modelling. Cited in our refactoring-ROI risk math.
- codedebtcost.com - Synonym-adjacent peer on the technical-debt head term.
- reworkcost.com - The broader rework-economics view (engineering plus manufacturing plus construction).
CodeSmellCost.com is independent. It is not a reseller of SonarQube, CodeScene, Sourcegraph, GitHub, or any other tool reviewed on the site. It is not a consulting lead-generation funnel disguised as content; the consulting CTA on the home page is honest, but the site stands on its own as a reference whether anyone hires Digital Signet or not.
The editorial position rests on three sources of authority. First, Fowler's Refactoring as the canonical vocabulary. Second, the peer-reviewed empirical software engineering literature (Bavota 2015, Bird 2011, Rahman 2025) for the correlation between smell density and defect rate. Third, named industry research with public methodology (DORA State of DevOps, Stripe Developer Coefficient, Pluralsight State of Developer Onboarding) for the productivity-cost translation.
The site deliberately does not chase vendor-pricing SEO. There is no /sonarqube-pricing page, no /jetbrains-pricing page. The /tools page compares the eight tools that matter for smell detection in 2026 but does not rank them with affiliate-driven scores. Where pricing changes (the tools page is monthly verified), the change ships with the next refresh pass.
Source pattern
Every dollar figure traces to a named source: Fowler's Refactoring 2nd edition, Robert C. Martin's Clean Code, peer-reviewed empirical studies (Bavota ICSE 2015, Bird FSE 2011, Rahman 2025 meta-study), or industry research (Stripe Developer Coefficient, DORA State of DevOps, Pluralsight onboarding). If a number cannot be traced, it does not ship.
No paid placements
No sponsored sections. No paid product placement. Book and tool links use affiliate parameters where available, disclosed in the footer, but the editorial selection is independent of commission.
No affiliate noise
Affiliate parameters appear on a small number of book and tool links and are disclosed. They never gate access to research, calculators, or methodology pages.
Monthly verification
Numbers, cited sources, and tool pricing get a first-business-week pass each month. LAST_VERIFIED_DATE in src/lib/schema.ts rolls forward when the pass finishes; everything on the site reads from that single source.
Single-source freshness
The header date stamp, the footer disclosure, the Article schema dateModified, and every per-page 'last verified' badge all read the same constant. One change, one consistent freshness signal.
Conservative cost ranges
All dollar bands assume a team of 8 engineers at fully-loaded cost and use the lower bound of cited research effect sizes. Ranges, never point estimates. An engineering leader presenting a range is more credible than one presenting a single number.
Cost ranges per smell are derived from four components: PR review drag (Cisco / SmartBear 2007 reviewer-effectiveness research), incident cost (Bird et al. FSE 2011 on ownership fragmentation; Rahman 2025 on defect density), story-point drag (DORA State of DevOps 2024 on rework-percentage by performance tier), and onboarding drag (Pluralsight State of Developer Onboarding 2024 on ramp time). Each component scales with team size, fully-loaded engineer cost, and a severity multiplier.
For the full source list, the per-component formula, the severity multiplier table, and the limitations: see the methodology page. Or run the model with your own numbers on the calculator.
Found a number that looks wrong, a citation that does not check out, or a smell missing from the catalog? Email [email protected]. Corrections turn around in 5 business days. The corrected version ships with the next monthly refresh pass and rolls the LAST_VERIFIED_DATE forward.
For the two-week code-debt audit consulting engagement (we run the model with your real incident history, PR review data, and onboarding records, and deliver the memo your leadership team will sign), the same address. Honest report whether the recommendation is “refactor now” or “this is defensible.”
Disclosures
CodeSmellCost.com is an independent editorial site published by Digital Signet. Some links on this site (notably to books on the books-and-references page and to tool vendor home pages on the tools page) are affiliate links. If you buy a book or subscribe to a tool through them, Digital Signet may earn a small commission at no cost to you. Affiliate selection does not influence editorial coverage.
This site is not affiliated with Martin Fowler, Pearson, Addison-Wesley, O'Reilly, SonarSource, CodeScene, Sourcegraph, GitHub, JetBrains, or any other publisher, author, or vendor mentioned. Quotes are attributed to their original sources. Trademarks remain the property of their respective owners.