# Code Quality — Daily DevOps & .NET > Explore articles about code quality, clean code principles, maintainability, and software craftsmanship practices that help teams build better software. Source: https://daily-devops.net/tags/codequality/ Generated: 2026-05-28 ## About this topic - [Topic landing page](https://daily-devops.net/tags/codequality/): Explore articles about code quality, clean code principles, maintainability, and software craftsmanship practices that help teams build better software. - [Back to all topics](https://daily-devops.net/tags/) - [Site index](https://daily-devops.net/llms.txt) ## Articles tagged "Code Quality" (23) - [I'm Done Making Empty Promises](https://daily-devops.net/posts/code-as-legacy-empty-promises/): // TODO: fix this properly. We'll refactor after the release. Tests when the API stabilizes. I've made every one of these promises. I'm done. - [My Biggest Enemy Writes My Code](https://daily-devops.net/posts/code-as-legacy-past-self/): Past Self is the most dangerous engineer on your team: skilled, well-intentioned, and gone when the bill comes due. This is about the code he left behind. - [The Code You Write Today Is Someone's Problem Tomorrow](https://daily-devops.net/posts/code-as-legacy/): Code is not just something you write—it is something you leave behind. After nearly two decades in production, here is what treating code as legacy means. - [AI Code Review Is a Sycophant: Why It Always Approves](https://daily-devops.net/posts/ai-code-review-is-a-sycophant/): Copilot and Claude find real bugs, but miss wrong abstractions and bad designs. Understanding that gap matters more than debating the tools. - [Your Privacy Docs Are Fiction: Let's Fix That with .NET CLI Tools](https://daily-devops.net/posts/privacy-audit-automation-dotnet-cli/): Quarterly audits can't catch PII added last Tuesday. Build .NET CLI tools that make compliance a build-time fact, not a spreadsheet fantasy. - [Certified, Filed, Forgotten: The Compliance Trainwreck](https://daily-devops.net/posts/compliance-verification-dotnet-cli/): Consultants paid. Docs filed. Then compliance becomes a Word doc ritual until an audit exposes the drift. CLI tools fix what checklists never could. - [Your Incident Response Plan Is a Lie. Here's How to Fix It.](https://daily-devops.net/posts/incident-response-github-actions/): ISO 27001 demands effective incident response. GitHub Actions transforms your dusty Word doc into automated workflows that actually work at 3 AM. - [Stop Hoarding Personal Data in Entity Framework](https://daily-devops.net/posts/data-minimization-entity-framework/): Monolithic user entities make GDPR deletion impossible. Separate operational from personal data in EF Core with nullable, purpose-documented fields. - [Real Professional Software Engineering in the AI Era](https://daily-devops.net/posts/real-professional-software-engineering-ai-era/): AI generates code instantly. Professionals spot when it is subtly wrong, debug failures AI cannot reason about, and see through the productivity narrative. - [The Feedback Loop That AI Can't Replace](https://daily-devops.net/posts/feedback-loop-ai-cant-replace/): Compilers validate logic, profilers expose performance lies, and production reveals every deferred decision. AI cannot close that feedback loop for you. - [Kehrwoche: What Swabian Cleaning Teaches About Technical Debt](https://daily-devops.net/posts/kehrwoche-technical-debt/): A Swabian tradition reveals why small, routine maintenance beats big cleanup initiatives—and what software teams get wrong about technical debt. - [Alphabet Soup: The Format Buffet Nobody Ordered](https://daily-devops.net/posts/alphabet-soup-file-formats/): CSV breaks on commas. YAML breaks on spaces. JSON breaks on trailing commas. TOML, TAML, TOON, CCL joined the chaos. Nobody wins. Here's why. - [Why Real Professionals Will Never Be Replaced by AI](https://daily-devops.net/posts/code-sharpens-thinking/): Typing code is trivial now—AI does it instantly. So why will real professionals never be replaced? Because vibe coding collapses under production reality. - [Most Software Teams Are Lying to Themselves—2026 Needs to Be Different](https://daily-devops.net/posts/happy-new-year-2026/): Stop promising to fix technical debt next quarter. .NET 10, analyzers, and tests are ready in 2026; only the engineering discipline is missing. - [Power of Ten Rules: More Relevant Than Ever for .NET](https://daily-devops.net/posts/dotnet-power-of-ten-rules/): Holzmann's safety-critical coding rules hit harder in modern C#: Roslyn analyzers, nullable types, and the type system enforce what C only wished. - [Code Metrics and Configuration: Beyond the Numbers Game](https://daily-devops.net/posts/code-metrics-configuration/): A critical look at .NET and Visual Studio code metrics, their configuration, and why context matters infinitely more than arbitrary thresholds. - [.NET 10: Boring by Design, Reliable by Default](https://daily-devops.net/posts/dotnet-10-released/): .NET 10 ships JIT physical promotion, AVX 10.2 loop vectorization, and C# 14 with LTS support through November 2028. Boring is finally the feature. - [How SearchValues Saved Us From Scaling Hell](https://daily-devops.net/posts/searchvalues-saved-us-from-scaling-hell/): How SearchValues in .NET 8-10 delivered 5x faster string operations, reduced infrastructure costs, and evolved with multi-substring optimization. - [Clean Code: A Lip Service, Not a Standard](https://daily-devops.net/posts/clean-code-lip-service-not-a-standard/): How misunderstood Clean Code ideals harm .NET systems. Learn to recognize code quality failures and apply C# best practices for maintainable software. - [Buzzword-Driven Development vs. Fundamental Software Quality](https://daily-devops.net/posts/buzzword-driven-development/): Why fundamental .NET software quality must never be sacrificed for trendy buzzwords, including recommended analyzers, settings, and practices. - [Vibe Coding in .NET: Creative Catalyst or Maintenance Risk?](https://daily-devops.net/posts/vibe-coding-isnt-wrong-its-unfinished/): Explore the balance between intuitive coding and structured development in .NET, examining when vibe coding helps and when it hinders project success. - [Managing Errors, Warnings, and Configurations in C# and .NET](https://daily-devops.net/posts/managing-errors-warnings-and-configurations/): Learn strategies for managing static code analysis warnings, improving code quality, configuring analyzers, and integrating into CI/CD pipelines. - [Introducing Nullability in Legacy .NET Code](https://daily-devops.net/posts/introducing-nullability-in-legacy-code/): Step-by-step guide for implementing nullable reference types in legacy .NET and C# codebases with practical strategies, patterns, and best practices. ## Optional - [Full site index for LLMs](https://daily-devops.net/llms.txt) - [Full content of all articles](https://daily-devops.net/llms-full.txt) - [RSS for this tag](https://daily-devops.net/tags/codequality/feed.rss) - [Atom for this tag](https://daily-devops.net/tags/codequality/feed.atom) - [JSON Feed for this tag](https://daily-devops.net/tags/codequality/feed.json)