<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code Quality on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/code-quality/</link><description>Recent content in Code Quality on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 17 Apr 2022 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/code-quality/index.xml" rel="self" type="application/rss+xml"/><item><title>Python Engineering (4): Type Hints, Linting, and Code Quality</title><link>https://www.chenk.top/en/python-engineering/04-type-hints-and-linting/</link><pubDate>Sun, 17 Apr 2022 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/python-engineering/04-type-hints-and-linting/</guid><description>&lt;p>Code reviews should be about logic and design, not about whether someone used single quotes or double quotes. Formatting debates are a waste of engineering time. The solution is to let machines handle style and let humans focus on correctness.&lt;/p>
&lt;p>This article covers three layers of automated code quality: type hints catch logical errors before runtime, linters catch style violations and common bugs, and pre-commit hooks enforce everything automatically on every commit.&lt;/p></description></item></channel></rss>