Static Code Analysis on Marko Apfelhttp://blog.marko-apfel.de/tags/static-code-analysis/Recent content in Static Code Analysis on Marko ApfelHugoen-USWed, 04 Feb 2026 14:00:02 +0100The Agreed Static Code Analysis Rule Set: Production vs. Non-Productionhttp://blog.marko-apfel.de/posts/static-code-analysis-ruleset/Wed, 04 Feb 2026 14:00:02 +0100http://blog.marko-apfel.de/posts/static-code-analysis-ruleset/Consistency across repositories, not theoretical perfection: how a Community of Practice settled on a static analysis rule set that treats production and non-production code differently on purpose.Wiring Up Static Code Analysis via Directory.Build.propshttp://blog.marko-apfel.de/posts/incorporating-static-code-analysis/Wed, 04 Feb 2026 14:00:02 +0100http://blog.marko-apfel.de/posts/incorporating-static-code-analysis/A working Directory.Build.props for incorporating Microsoft’s analyzers and StyleCop across an entire repository, with production code held to a stricter bar than tests and tooling.Brownfield vs. Greenfield: Why One Static-Analysis Ruleset Doesn't Fit Bothhttp://blog.marko-apfel.de/posts/brownfield-vs-greenfield-rulesets/Thu, 05 Sep 2024 18:48:29 +0200http://blog.marko-apfel.de/posts/brownfield-vs-greenfield-rulesets/One uniform static-analysis ruleset across an entire codebase sounds principled — until that codebase includes both a decade-old legacy module and code written last week.Why Test Code Deserves a More Relaxed Static-Analysis Rulesethttp://blog.marko-apfel.de/posts/production-vs-non-production-rulesets/Thu, 05 Sep 2024 18:48:29 +0200http://blog.marko-apfel.de/posts/production-vs-non-production-rulesets/Production code and test code are trying to do genuinely different jobs — holding both to identical static-analysis rules tends to slow down the wrong thing without protecting the right one.