madtypes VS ruff

Hei !

This comment inspired me because I was working on data-types at my company at the moment and I realized how static typing would have really benefited us.

So I made a library that does just that !

https://github.com/6r17/madtypes

I hope this will help some people !

Now that I have started my Python project devto-followers2md, I have recently started checking my code with Ruff, a fast Rust-based Python linter and code formatter. I also started using pyright, (yes, I know it is very ironic, it is made by Microsoft), and will be working on making sure the project aligns with its standards too.

A layer of deterministic constraints: checks that keep the output converging toward quality instead of tech debt. I work in Python, so for me that's ruff, ty, tach run through prek, plus gitleaks and a stack of project-specific hooks. Different language, different tools — the constraint is the point, not the toolchain.

Is this reasoning, or measurement? If measurement, push it to a deterministic tool. Sonar, Spotless, Ruff, ESLint, coverage gates, pre-commit hooks, complexity calculators. Write a script if no tool exists. That's how just lint got built, and that's the Unix-philosophy move for agentic coding. Hooks fire on tool calls; CI fires on PRs; pre-commit fires on commit. Pick the cheapest layer that catches the failure and run it there.

We ran ruff with the AIR301 and AIR302 rules to catch most of these automatically:

Ruff has rapidly become the default Python linter for modern development teams. Written in Rust, it executes 10-100x faster than traditional Python linters like Flake8, Pylint, and isort. But speed is only part of the story - Ruff reimplements over 800 lint rules from dozens of Flake8 plugins, pycodestyle, pyflakes, isort, and more, consolidating what used to require five or six separate tools into a single binary with a single configuration file.

The canary in the coal mine: Watch the GitHub issue response times. If community-filed issues start getting slower responses while Codex-related issues get instant attention, you'll know the roadmap has shifted. Set up GitHub notifications on the uv and Ruff repos now.

The better approach: let the agent write code however it wants, then run Prettier, Black, Ruff, or ESLint. Zero ambiguity. The agent doesn't need to think about formatting at all, which means fewer tokens spent and fewer decisions that could go wrong.

So I started with my first issue on ruff & made the PR, Since it was a tracking issue with many related problems, I kept digging deeper. Over time, that curiosity led to 20+ merged PRs in ruff.