<?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://shio-chan-dev.github.io/jeanblog/zh/tags/%E9%A3%8E%E9%99%A9/</link><description>Recent content in 风险 on Jeanphilo Blog</description><generator>Hugo -- 0.159.2</generator><language>zh-cn</language><lastBuildDate>Sat, 24 Jan 2026 12:50:25 +0800</lastBuildDate><atom:link href="https://shio-chan-dev.github.io/jeanblog/zh/tags/%E9%A3%8E%E9%99%A9/index.xml" rel="self" type="application/rss+xml"/><item><title>项目长期延期怎么办：诊断、止血与重启</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/management/long-delayed-project/</link><pubDate>Sat, 24 Jan 2026 12:50:25 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/management/long-delayed-project/</guid><description>给出项目延期的诊断方法与可执行的止血策略。</description></item><item><title>缓存什么时候危险：一致性、失效与业务风险</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/caching-when-dangerous/</link><pubDate>Sat, 24 Jan 2026 12:23:30 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/caching-when-dangerous/</guid><description>说明缓存何时会带来风险，并给出适用条件与规避策略。</description></item><item><title>为什么不该自己设计密码学：风险、误区与替代方案</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/security/why-not-roll-your-own-crypto/</link><pubDate>Sat, 24 Jan 2026 11:11:28 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/security/why-not-roll-your-own-crypto/</guid><description>解释自创密码学为何高风险，并给出工程上更安全的替代做法。</description></item></channel></rss>