The lazy developer's code quality
The article discusses a developer's journey to improve code quality in a Python project by adopting modern tools that minimize manual effort. The author evaluates and selects a streamlined toolchain including uv, ruff, pyright, and pre-commit to handle environment management, formatting, linting, and type checking. The focus is on reducing configuration overhead while maintaining high code standards, with reflections on the limitations of tools like pylint in understanding context and testing frameworks.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3872509) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Alessandra Bilardi Posted on Apr 30 • Originally published at alessandra.bilardi.net The lazy developer's code quality #pytest #ruff #pyright #uv A repo to refresh, several rabbit holes to dive into A while ago, at PyCon IT, I attended a talk that opened my eyes on pytest: simpler test management, especially for mocks parametrizable fixtures instead of the setUp / tearDown ritual bare assert instead of a thousand self.assertEqual I'd like my repo python-prototype, born for…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
