<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>可读性 on Jeanphilo Blog</title><link>https://jeanphilogong.github.io/jeanblog/zh/tags/%E5%8F%AF%E8%AF%BB%E6%80%A7/</link><description>Recent content in 可读性 on Jeanphilo Blog</description><generator>Hugo -- 0.168.0</generator><language>zh-cn</language><lastBuildDate>Wed, 03 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://jeanphilogong.github.io/jeanblog/zh/tags/%E5%8F%AF%E8%AF%BB%E6%80%A7/index.xml" rel="self" type="application/rss+xml"/><item><title>函数命名不是取名字：它是在描述系统边界</title><link>https://jeanphilogong.github.io/jeanblog/zh/dev/python/function-naming-design-intent/</link><pubDate>Wed, 03 Jun 2026 00:00:00 +0000</pubDate><guid>https://jeanphilogong.github.io/jeanblog/zh/dev/python/function-naming-design-intent/</guid><description>用一个小型 graph pipeline runner 解释 get、resolve、validate、ready、skip 等函数命名如何表达行为、失败语义和副作用。</description></item><item><title>什么样的代码可读性强：结构、命名与认知负担</title><link>https://jeanphilogong.github.io/jeanblog/zh/dev/engineering/readable-code-principles/</link><pubDate>Sat, 24 Jan 2026 13:27:25 +0800</pubDate><guid>https://jeanphilogong.github.io/jeanblog/zh/dev/engineering/readable-code-principles/</guid><description>从结构、命名与认知负担角度定义“可读性强的代码”。</description></item><item><title>匿名函数的价值：快速封装与局部表达</title><link>https://jeanphilogong.github.io/jeanblog/zh/dev/language/anonymous-functions-uses/</link><pubDate>Sat, 24 Jan 2026 13:04:00 +0800</pubDate><guid>https://jeanphilogong.github.io/jeanblog/zh/dev/language/anonymous-functions-uses/</guid><description>说明匿名函数的用途、适用场景与常见误区。</description></item><item><title>什么是好代码：可读、可测、可演进</title><link>https://jeanphilogong.github.io/jeanblog/zh/dev/engineering/what-is-good-code/</link><pubDate>Sat, 24 Jan 2026 12:33:47 +0800</pubDate><guid>https://jeanphilogong.github.io/jeanblog/zh/dev/engineering/what-is-good-code/</guid><description>从可读性、正确性与演进成本出发定义好代码，并给出可执行的判断清单。</description></item></channel></rss>