{"canonical_url":"https://engineer.company/portfolio/set-a-zero-warnings-bar-across-six-languages/","content_markdown":"# Set a zero‑warnings bar across six languages\n\nSet a zero‑warnings quality bar across six languages — Go, TypeScript, SQL, Python, Shell and Markdown — enforced by pre‑commit hooks.\n\n2025\n\n**Situation.** Warnings that pile up are quietly corrosive. Every diagnostic you ignore lowers the bar a little, and once the build spits out forty of them nobody reads any of them, and a real problem sits in that list in plain sight because \"warnings\" have become background noise. In a polyglot codebase there are that many more sources of noise to let it happen.\n\n**Task.** The repo needed one uncompromising quality bar across every language, so things got fixed instead of accumulating.\n\n**Action.** A zero‑warnings policy went in, with the tooling as the thing that enforces it, because a policy that relies on everyone's vigilance loses to the first busy week. Every linter diagnostic is an error — there's no \"warn\" tier to hide in — and it's the same across the whole stack: Go with golangci‑lint, TypeScript with ESLint, SQL with SQLFluff, Python with Ruff, shell with ShellCheck, Markdown with markdownlint. Inline suppressions are banned, so you can't paper over a diagnostic; you have to actually fix the thing. Pre‑commit and pre‑push hooks run the linters and the tests; failures in the covered rule and test set block the corresponding commit or push. There are even function- and file‑length limits, to keep modules from sprawling past the point of being readable.\n\n**Result.** Problems get fixed at the source instead of deferred into a backlog nobody clears, and the codebase stays clean by default rather than by periodic heroics. The standard is identical whatever language you're in, and it's the tooling holding it — not anyone's willpower — which is why it actually holds.\n\n---\n\n- Role: Head of Engineering\n- Categories: [DevOps](https://advisory.engineer.company/categories/devops/), [Automation \u0026 CI/CD](https://advisory.engineer.company/categories/automation/), [Testing \u0026 QA](https://advisory.engineer.company/categories/testing/), [Technical Leadership](https://advisory.engineer.company/categories/technical-leadership/), [Documentation](https://advisory.engineer.company/categories/documentation/)\n- Services: [DevOps \u0026 CI/CD Automation](https://advisory.engineer.company/services/devops-cicd/), [Technical Leadership \u0026 Consulting](https://advisory.engineer.company/services/technical-leadership/)\n\n\u003chttps://engineer.company/portfolio/set-a-zero-warnings-bar-across-six-languages/\u003e\n","date_modified":"2026-11-12T05:34:23Z","description":"Set a zero-warnings quality bar across Go, TypeScript, SQL, Python, Shell and Markdown, enforced by pre-commit hooks.","formats":{"gemtext":"https://advisory.engineer.company/portfolio/set-a-zero-warnings-bar-across-six-languages/index.gmi","gopher":"https://advisory.engineer.company/portfolio/set-a-zero-warnings-bar-across-six-languages/gophermap","html":"https://advisory.engineer.company/portfolio/set-a-zero-warnings-bar-across-six-languages/","json":"https://advisory.engineer.company/portfolio/set-a-zero-warnings-bar-across-six-languages/index.json","markdown":"https://advisory.engineer.company/portfolio/set-a-zero-warnings-bar-across-six-languages/index.md","pdf":"https://advisory.engineer.company/portfolio/set-a-zero-warnings-bar-across-six-languages/index.pdf"},"kind":"page","language":"en","title":"Set a zero-warnings bar across six languages","url":"https://advisory.engineer.company/portfolio/set-a-zero-warnings-bar-across-six-languages/","version":1}