<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>沉默土豆的烹饪指南</title><description>Liyuk 关于技术、工作与日常的写作。</description><link>https://liyuk.com/</link><language>zh-CN</language><item><title>两个人的记忆地图：一份可自托管的纪念站模板</title><link>https://liyuk.com/projects/2026/10/astro-memory-atlas/</link><guid isPermaLink="true">https://liyuk.com/projects/2026/10/astro-memory-atlas/</guid><description>一个用 Astro 搭建的双语纪念站模板，把回忆整理成相册、关系时间线、年度回顾和地点地图，并介绍一套借助 AI 整理内容的维护流程。</description><pubDate>Wed, 07 Oct 2026 00:00:00 GMT</pubDate><atom:updated>2026-10-07T00:00:00.000Z</atom:updated><category>project</category><category>astro</category><category>static-site</category><category>privacy</category><category>relationships</category><category>personal-publication</category></item><item><title>纪念碑谷</title><link>https://liyuk.com/photos/monument-valley-2/</link><guid isPermaLink="true">https://liyuk.com/photos/monument-valley-2/</guid><description>错视长阶、云间列车、漂浮小岛和水边的小猫，串起了纪念碑谷的新一段旅程；感谢瑶子的创意和生产力。</description><pubDate>Tue, 29 Sep 2026 00:00:00 GMT</pubDate><atom:updated>2026-09-29T00:00:00.000Z</atom:updated><category>gallery</category></item><item><title>盼东归</title><link>https://liyuk.com/projects/2026/08/novel-pandonggui/</link><guid isPermaLink="true">https://liyuk.com/projects/2026/08/novel-pandonggui/</guid><description>一部长篇小说。陆昭自幼在西域明教长大，身上挂着一块写着&quot;长生&quot;的长命锁。十九岁奉命踏入潼关，在战乱中传信、领路、救人——一个普通人，能不能不被门派、家族和历史替自己决定人生。</description><pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-09-28T00:00:00.000Z</atom:updated><category>project</category><category>fiction</category><category>novel</category><category>work-leadership</category></item><item><title>愿望之后</title><link>https://liyuk.com/projects/2026/08/novel-yuanwang-zhihou/</link><guid isPermaLink="true">https://liyuk.com/projects/2026/08/novel-yuanwang-zhihou/</guid><description>一部长篇小说。席班抱着三个月大的沈乐走进沙海，只想带这个孩子活着穿过商路。愿望从不保证幸福，它只会把责任留给愿望实现之后的人。</description><pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-09-28T00:00:00.000Z</atom:updated><category>project</category><category>fiction</category><category>novel</category><category>work-leadership</category></item><item><title>Engineering Decision Skills：评审、排期、复盘时，我想让 AI 多做一步</title><link>https://liyuk.com/projects/2026/09/engineering-decision-skills/</link><guid isPermaLink="true">https://liyuk.com/projects/2026/09/engineering-decision-skills/</guid><description>方案明天要评审，三件事排不进一个双月，项目又延期了：五个独立 Skill，各给一份具体输入和可直接拿去讨论的产出。</description><pubDate>Mon, 28 Sep 2026 00:00:00 GMT</pubDate><atom:updated>2026-09-28T00:00:00.000Z</atom:updated><category>project</category><category>agent</category><category>technical-management</category><category>decision-making</category><category>metrics</category><category>workflow</category><category>open-source</category></item><item><title>RelationForge：看清一段互动，再决定怎么回应</title><link>https://liyuk.com/projects/2026/09/relation-forge/</link><guid isPermaLink="true">https://liyuk.com/projects/2026/09/relation-forge/</guid><description>有些关系让人不舒服，却又说不清哪里不对。我希望 RelationForge 能帮人把事情理清楚些，也看看自己在其中做了什么。</description><pubDate>Mon, 28 Sep 2026 00:00:00 GMT</pubDate><atom:updated>2026-09-28T00:00:00.000Z</atom:updated><category>project</category><category>agent</category><category>interpersonal-analysis</category><category>anti-scam</category><category>privacy</category><category>workflow</category></item><item><title>产品资源排不上，研发接下项目后怎么推进？</title><link>https://liyuk.com/consulting/2026/09/product-engineer-without-boundaries/</link><guid isPermaLink="true">https://liyuk.com/consulting/2026/09/product-engineer-without-boundaries/</guid><description>一次关于高压工作与复合岗位的咨询：先看清自己经历了什么、已经做了什么，再把产品工程师的能力挑战和下一步拆开。</description><pubDate>Wed, 23 Sep 2026 00:00:00 GMT</pubDate><atom:updated>2026-09-23T00:00:00.000Z</atom:updated><category>consulting</category><category>career-development</category><category>engineering</category><category>product-thinking</category><category>operations</category><category>communication</category><category>collaboration</category><category>prioritization</category><category>risk-management</category></item><item><title>从做项目到做交易</title><link>https://liyuk.com/writing/2026/09/every-choice-is-a-trade/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/09/every-choice-is-a-trade/</guid><description>从供需关系和出入场时机，回看企业发展、创业项目与金融交易中的资源投入。</description><pubDate>Thu, 17 Sep 2026 00:00:00 GMT</pubDate><atom:updated>2026-09-17T00:00:00.000Z</atom:updated><category>writing</category><category>decision-making</category><category>product</category><category>strategy</category><category>reflection</category><category>risk-management</category><category>agency</category></item><item><title>缓存究竟在哪里：多层执行服务的局部性</title><link>https://liyuk.com/writing/2026/08/cache-optimization-and-locality/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/cache-optimization-and-locality/</guid><description>以一套多层执行服务为例，拆解请求身份、边缘路由、执行资源和后端缓存的多级局部性，并给出可复用的路由、失效、故障转移与观测方案。</description><pubDate>Fri, 28 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-09-04T00:00:00.000Z</atom:updated><category>writing</category><category>performance</category><category>systems-design</category><category>algorithms</category><category>reliability</category><category>observability</category><category>routing</category><category>technology</category></item><item><title>数据中心不是报表：从数据生产到业务判断</title><link>https://liyuk.com/writing/2026/08/data-center-revenue-design/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/data-center-revenue-design/</guid><description>从分析、经营和工程的不同问题出发，整理一个多来源业务平台的数据中心应该如何划分 Tab、定义指标、组织读写链路，以及怎样处理计费、对账、增长和成本。</description><pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-09-04T00:00:00.000Z</atom:updated><category>writing</category><category>data</category><category>metrics</category><category>systems-design</category><category>observability</category><category>settlement</category><category>reliability</category><category>technical-planning</category><category>architecture</category><category>risk-management</category></item><item><title>从一次请求看多节点执行系统的架构演进</title><link>https://liyuk.com/writing/2026/08/distributed-architecture-is-state-ownership/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/distributed-architecture-is-state-ownership/</guid><description>从一套多节点执行系统的故障结构出发，复盘请求、状态、存储、性能和故障如何逐渐跨越边界，并讨论下一版架构应该怎样重新组织。</description><pubDate>Fri, 28 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-09-04T00:00:00.000Z</atom:updated><category>writing</category><category>systems-design</category><category>architecture</category><category>distributed-work</category><category>reliability</category><category>observability</category><category>capacity-planning</category><category>technology</category></item><item><title>从一个 Request ID 开始：我给小项目做了一套简配的可观测与稳定性系统</title><link>https://liyuk.com/writing/2026/08/from-request-id-to-trace-system/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/from-request-id-to-trace-system/</guid><description>从一个小型 API 服务的观测问题出发，借鉴成熟可观测平台的经验，整理 Request ID、分布式 Trace、服务发现、健康监测、日志查询、稳定性和基础设施治理的最小实现。</description><pubDate>Tue, 25 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-09-04T00:00:00.000Z</atom:updated><category>writing</category><category>observability</category><category>reliability</category><category>systems</category><category>technology</category><category>operations</category></item><item><title>AI Gateway：从后端调度到成本治理</title><link>https://liyuk.com/writing/2026/09/what-ai-gateways-do/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/09/what-ai-gateways-do/</guid><description>通过多后端模型访问场景，理解 AI Gateway 如何处理资源调度、容量控制、故障切换、分布式状态、用量统计和企业成本治理。</description><pubDate>Thu, 03 Sep 2026 00:00:00 GMT</pubDate><atom:updated>2026-09-03T00:00:00.000Z</atom:updated><category>writing</category><category>ai</category><category>architecture</category><category>systems-design</category><category>routing</category><category>reliability</category><category>capacity-planning</category><category>observability</category><category>interview</category><category>learning</category><category>technology</category></item><item><title>让差异停留在配置层：多业务域平台的架构设计</title><link>https://liyuk.com/writing/2026/08/configuration-driven-multi-domain-platform/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/configuration-driven-multi-domain-platform/</guid><description>内容、搜索、交易和增长系统在多国家、多行业和多场景下会反复遇到同一个问题：如何复用稳定能力，又让业务表达保持差异。配置、协议、组件和编排，应该怎样划分边界。</description><pubDate>Sat, 29 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-29T00:00:00.000Z</atom:updated><category>writing</category><category>architecture</category><category>systems-design</category><category>technical-planning</category><category>technology</category><category>operations</category></item><item><title>AI 写得很好，但这真的是我想说的吗？</title><link>https://liyuk.com/writing/2026/08/what-i-meant-and-what-ai-wrote/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/what-i-meant-and-what-ai-wrote/</guid><description>一次关于 AI 使用的经验分享：它可以把人已有的事实、感受和逻辑整理得更清楚，却不能替人积累知识、形成判断。人在使用 AI 时，也需要警惕被内容和工作状态推着走的感觉。</description><pubDate>Fri, 28 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-28T00:00:00.000Z</atom:updated><category>writing</category><category>ai</category><category>writing</category><category>agency</category><category>human-ai-collaboration</category><category>provenance</category><category>judgment</category></item><item><title>一个营销活动是怎样变成增长系统的：从交易事实到可审计权益</title><link>https://liyuk.com/writing/2026/08/referral-rewards-fraud-control/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/referral-rewards-fraud-control/</guid><description>从裂变奖励和交易系统出发，设计一套可复用、可审计的营销基础设施，覆盖活动、受众、权益、预算、归因、风控、实验、触达和效果分析。</description><pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-27T00:00:00.000Z</atom:updated><category>writing</category><category>systems-design</category><category>risk-management</category><category>anti-scam</category><category>settlement</category><category>reliability</category><category>observability</category><category>operations</category><category>workflow</category><category>data</category><category>auditability</category></item><item><title>AI 不会自动带来生产力：从局部提速到系统价值</title><link>https://liyuk.com/writing/2026/08/ai-productivity-complex-systems/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/ai-productivity-complex-systems/</guid><description>从一次多系统对接经历出发，区分创造、任务效率、组织生产力和经营价值，讨论 AI 进入复杂系统后，收益到底从哪里来、成本又该怎么算。</description><pubDate>Wed, 26 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-26T00:00:00.000Z</atom:updated><category>writing</category><category>ai</category><category>developer-productivity</category><category>systems</category><category>systems-design</category><category>architecture</category><category>metrics</category><category>observability</category><category>technical-planning</category><category>strategy</category></item><item><title>AI 方案怎么卖给老板：从技术价值到 B2B 生意</title><link>https://liyuk.com/consulting/2026/08/turning-ai-into-business-value/</link><guid isPermaLink="true">https://liyuk.com/consulting/2026/08/turning-ai-into-business-value/</guid><description>一场关于 FDE 会议、技术沟通和 AI 商业价值的咨询对话：当老板关心收入和成本时，技术人员该怎样把能力讲成对方听得懂、愿意验证的结果。</description><pubDate>Wed, 26 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-26T00:00:00.000Z</atom:updated><category>consulting</category><category>ai</category><category>communication</category><category>product-thinking</category><category>strategy</category><category>metrics</category><category>operations</category><category>engineering</category><category>career-development</category></item><item><title>A 同学：刚加入新团队，怎么找到自己的工作入口？</title><link>https://liyuk.com/consulting/2026/08/newcomer-without-a-map/</link><guid isPermaLink="true">https://liyuk.com/consulting/2026/08/newcomer-without-a-map/</guid><description>入职两个月只有需求，怎么从“证明自己”走到下一步？一场关于新组织、汇报关系、业务上下文和资深工程师如何开始行动的咨询访谈。</description><pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-21T00:00:00.000Z</atom:updated><category>consulting</category><category>career-development</category><category>onboarding</category><category>organization</category><category>network</category><category>authorization</category><category>growth</category><category>communication</category><category>collaboration</category></item><item><title>dsh-skin-chatlab 2.x：把 DSH Web 变成可切换的聊天工作台</title><link>https://liyuk.com/projects/2026/08/dsh-skin-chatlab-upgrade/</link><guid isPermaLink="true">https://liyuk.com/projects/2026/08/dsh-skin-chatlab-upgrade/</guid><description>从一套飞书视觉适配扩展到六套独立皮肤，并补齐聚合加载、头像身份收敛、部分安装回退和可卸载边界。</description><pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-21T00:00:00.000Z</atom:updated><category>project</category><category>technology</category><category>agent-systems</category><category>developer-productivity</category></item><item><title>不只是模型切换：DSH Quota Router 的工程设计与路由算法</title><link>https://liyuk.com/projects/2026/08/quota-router-engineering/</link><guid isPermaLink="true">https://liyuk.com/projects/2026/08/quota-router-engineering/</guid><description>从候选链、失败分类、per-turn identity 到成本公式，解释一个可控、可审计的 DSH 多来源模型路由器如何工作。</description><pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-21T00:00:00.000Z</atom:updated><category>project</category><category>agent</category><category>routing</category><category>algorithms</category><category>reliability</category><category>observability</category><category>typescript</category></item><item><title>从能跑到可维护：我开发 DSH 插件时遇到的架构与稳定性问题</title><link>https://liyuk.com/writing/2026/08/dsh-plugin-architecture-stability/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/dsh-plugin-architecture-stability/</guid><description>基于 ChatLab、Agent Suite 与 Quota Router 的实际开发和调试，整理 DSH 插件机制、preview 版本的常见稳定性问题，以及自己开发插件时最容易踩到的边界。</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-20T00:00:00.000Z</atom:updated><category>writing</category><category>technology</category><category>agent-systems</category><category>developer-productivity</category></item><item><title>管理管理者如何找到、培养和交接负责人：HRBP、TA 与技术负责人的分工</title><link>https://liyuk.com/writing/2026/08/manager-of-managers-leadership-supply/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/manager-of-managers-leadership-supply/</guid><description>招聘不是把岗位交给 HR 或 TA，而是由管理管理者、HRBP、TA 和用人负责人共同建立一套从问题定义、招聘计划到培养接班的负责人来源与成长机制。</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-20T00:00:00.000Z</atom:updated><category>writing</category><category>management</category><category>hiring</category><category>organization</category><category>team</category><category>leadership</category><category>planning</category></item><item><title>人、事、钱：管理管理者必须理解的企业运作结构</title><link>https://liyuk.com/writing/2026/08/people-work-money-authority/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/people-work-money-authority/</guid><description>从人事权、问题与优先级决定权、预算与人员容量配置权三条线，解释管理管理者如何理解企业运作结构，判断自己能决定什么、需要协商什么、必须升级什么。</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-20T00:00:00.000Z</atom:updated><category>writing</category><category>management</category><category>leadership</category><category>organization</category><category>governance</category><category>decision-making</category><category>strategy</category></item><item><title>关键词与内容规模：从需求发现到页面治理</title><link>https://liyuk.com/writing/2026/08/seo-content-engineering/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/seo-content-engineering/</guid><description>页面数量涨了，真正被读、被用的页面却没有变多——这篇写给关键词扩展和内容生产装上台账、闸门和退出机制。</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-20T00:00:00.000Z</atom:updated><category>writing</category><category>seo</category><category>writing</category><category>ai</category><category>governance</category></item><item><title>SEO 实验与异常排查：用时间线保护判断</title><link>https://liyuk.com/writing/2026/08/seo-experiments/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/seo-experiments/</guid><description>处理延迟、CUPED 和流量污染很容易被一起误读成&quot;算法更新&quot;；这里记录的是先冻结时间线、再谈显著性的排查协议。</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-20T00:00:00.000Z</atom:updated><category>writing</category><category>seo</category><category>growth</category><category>engineering</category><category>metrics</category></item><item><title>提交、收录与流量恢复：把搜索运营做成可靠系统</title><link>https://liyuk.com/writing/2026/08/seo-indexing-recovery/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/seo-indexing-recovery/</guid><description>提交成功、抓取成功、索引成功和排名回升是四件不同的事；把它们混成一句&quot;收录了&quot;，流量事故就没法排查。</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-20T00:00:00.000Z</atom:updated><category>writing</category><category>seo</category><category>engineering</category><category>reliability</category><category>observability</category></item><item><title>外链与来源权威：从链接数量转向可引用关系</title><link>https://liyuk.com/writing/2026/08/seo-links/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/seo-links/</guid><description>外链数量和真实引荐是两件事：来源语境、目标页价值，比 DR、DA 这类第三方分数更值得盯。</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-20T00:00:00.000Z</atom:updated><category>writing</category><category>seo</category><category>backlinks</category><category>growth</category><category>trust</category></item><item><title>结构化数据与媒体 SEO：让页面事实可被理解</title><link>https://liyuk.com/writing/2026/08/seo-rich-media/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/seo-rich-media/</guid><description>alt 和 Schema 是事实核验之后的最后一步，不是第一步；标签补得再全，事实模型缺失，页面还是难懂。</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-20T00:00:00.000Z</atom:updated><category>writing</category><category>seo</category><category>image-seo</category><category>video-seo</category><category>architecture</category></item><item><title>SEO 搜索基础地图：从被发现到产生价值</title><link>https://liyuk.com/writing/2026/08/seo-search-fundamentals/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/seo-search-fundamentals/</guid><description>很多人从标题和关键词开始学 SEO，这篇建议倒过来：先看一条从被发现到产生价值的完整链路，再动手写字。</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-20T00:00:00.000Z</atom:updated><category>writing</category><category>seo</category><category>engineering</category><category>learning</category><category>systems-thinking</category><category>metrics</category></item><item><title>技术 SEO 底盘：URL、渲染、迁移与性能</title><link>https://liyuk.com/writing/2026/08/seo-technical-system/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/seo-technical-system/</guid><description>一篇内容如果有好几个能打开的地址，canonical、迁移和内链就会各说各话；页面合同先解决&quot;谁是这个页面&quot;。</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-20T00:00:00.000Z</atom:updated><category>writing</category><category>seo</category><category>engineering</category><category>systems</category><category>reliability</category></item><item><title>SEO 到 GEO：从可发现页面到可复查的回答证据</title><link>https://liyuk.com/writing/2026/08/seo-to-geo-engineering/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/seo-to-geo-engineering/</guid><description>被 AI 提到、被引用、引用内容真正支持答案，是三件不同的事；这里用一套证据状态机取代一个神秘的可见性分数。</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-20T00:00:00.000Z</atom:updated><category>writing</category><category>seo</category><category>ai</category><category>observability</category><category>explainability</category><category>information-architecture</category></item><item><title>SEO 价值不是流量：把搜索接到业务漏斗</title><link>https://liyuk.com/writing/2026/08/seo-value-funnel/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/seo-value-funnel/</guid><description>曝光涨了、下载没涨，问题不一定出在流量——这篇把 SEO 价值拆成搜索链和业务链，找瓶颈真正卡在哪一层。</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-20T00:00:00.000Z</atom:updated><category>writing</category><category>seo</category><category>growth</category><category>engineering</category><category>metrics</category></item><item><title>Fourfold</title><link>https://liyuk.com/projects/2026/08/astro-fourfold/</link><guid isPermaLink="true">https://liyuk.com/projects/2026/08/astro-fourfold/</guid><description>面向独立作者、工程师、研究者和创作者的静态优先个人出版物 starter，把写作、专栏、项目、研究、影像与发现组织成可持续的内容系统。</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-20T00:00:00.000Z</atom:updated><category>project</category><category>astro</category><category>static-site</category><category>personal-publication</category><category>information-architecture</category><category>open-source</category></item><item><title>二线管理的治理底线：安全、公平与权力如何被约束</title><link>https://liyuk.com/writing/2026/08/governance-boundaries-for-managers/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/governance-boundaries-for-managers/</guid><description>二线要对结果负责，但不应仅用结果交换安全、合规和公平；管理事故发生时，也不应只追个人，还要保护人、查清事实、留档并复盘组织条件。</description><pubDate>Wed, 19 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-19T00:00:00.000Z</atom:updated><category>writing</category><category>leadership</category><category>management</category><category>organization</category><category>risk-management</category><category>work-leadership</category></item><item><title>让执行交给 Agent：情绪适应、信任校准与人的压力释放</title><link>https://liyuk.com/research/2026/08/agent-hci-emotional-equilibrium/</link><guid isPermaLink="true">https://liyuk.com/research/2026/08/agent-hci-emotional-equilibrium/</guid><description>从长任务中的实际使用出发，讨论 Agent 如何依据不确定性、等待、失败和接管需求调节状态、证据与行动反馈；也记录执行委托如何改变人的压力、信任和能力边界。</description><pubDate>Wed, 19 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-19T00:00:00.000Z</atom:updated><category>research</category><category>hci</category><category>agent</category><category>agency</category><category>emotion</category><category>trust-calibration</category><category>cognitive-offloading</category><category>deskilling</category><category>observability</category></item><item><title>让 Agent 更像一个可以协作的对象：状态、反馈与结果确认</title><link>https://liyuk.com/research/2026/08/agent-interface-feedback-architecture/</link><guid isPermaLink="true">https://liyuk.com/research/2026/08/agent-interface-feedback-architecture/</guid><description>从 ChatLab 的实际设计出发，记录如何借用人和人协作中的在场、回应、等待和交付语法，让 Agent 的运行状态更容易被理解；这是一篇关于反馈、证据、关键介入和结果确认的 HCI 设计观察。</description><pubDate>Wed, 19 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-19T00:00:00.000Z</atom:updated><category>research</category><category>hci</category><category>agent</category><category>feedback</category><category>observability</category><category>recoverability</category><category>authorization</category><category>human-ai-collaboration</category><category>systems-design</category></item><item><title>先拆解，后调度：多模型任务拆解、能力切换与子任务路由研究综述</title><link>https://liyuk.com/research/2026/08/model-harness-task-scheduling-context-routing/</link><guid isPermaLink="true">https://liyuk.com/research/2026/08/model-harness-task-scheduling-context-routing/</guid><description>讨论任务开始阶段的拆解、子任务能力分类、模型选择与执行中切换，并将完整 Agent 调度理论收缩为 dsh-quota-router 的一个工程切片：已拆分子任务的模型能力路由与有界 fallback。</description><pubDate>Wed, 19 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-19T00:00:00.000Z</atom:updated><category>research</category><category>ai</category><category>agent-systems</category><category>engineering</category><category>architecture</category><category>planning</category><category>observability</category><category>measurement</category><category>systems</category></item><item><title>Quota Router：给 DSH 一条可解释的多源模型 fallback 链</title><link>https://liyuk.com/projects/2026/08/quota-router/</link><guid isPermaLink="true">https://liyuk.com/projects/2026/08/quota-router/</guid><description>DeepSeek Harness 的纯策略插件：按任务选择有序、可解释、可审计的模型候选链，并在配额、限流或传输失败时沿链有界前进。</description><pubDate>Wed, 19 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-19T00:00:00.000Z</atom:updated><category>project</category><category>agent</category><category>routing</category><category>algorithms</category><category>explainability</category><category>reliability</category><category>observability</category><category>typescript</category></item><item><title>管理管理者如何带团队，以及如何让权限和资源服务结果</title><link>https://liyuk.com/writing/2026/08/manager-of-managers-management-and-authority/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/manager-of-managers-management-and-authority/</guid><description>管理管理者既不能收回一线负责人的日常管理，也不能只靠口号推动协作；他需要在清楚的授权和资源条件下，让多个团队对共同结果负责。</description><pubDate>Mon, 17 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-17T00:00:00.000Z</atom:updated><category>writing</category><category>leadership</category><category>management</category><category>mentoring</category><category>team</category><category>decision-making</category><category>organization</category><category>work-leadership</category></item><item><title>为什么需要管理管理者，以及什么样的人适合这段责任</title><link>https://liyuk.com/writing/2026/08/managing-managers-and-leader-profile/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/managing-managers-and-leader-profile/</guid><description>多团队之间的资源和协作责任出问题时，光靠&quot;再加一个会协调的人&quot;解决不了；这一层该不该加、加了谁合适，最后都要落在同一个问题上——出了分歧，谁能拍板并承担代价。</description><pubDate>Mon, 17 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-17T00:00:00.000Z</atom:updated><category>writing</category><category>leadership</category><category>management</category><category>organization</category><category>team</category><category>work-leadership</category></item><item><title>怎么留与怎么补：让一线负责人形成可持续的接班安排</title><link>https://liyuk.com/writing/2026/08/sustaining-frontline-managers/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/sustaining-frontline-managers/</guid><description>人可以流动，岗位不必为了留人而虚设；二线真正要留下的，是负责目标所需的能力、关系和组织结果。</description><pubDate>Mon, 17 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-17T00:00:00.000Z</atom:updated><category>writing</category><category>leadership</category><category>management</category><category>growth</category><category>team</category><category>work-leadership</category></item><item><title>我的 DSH 工作台：九个插件</title><link>https://liyuk.com/writing/2026/08/dsh-plugin-toolbox/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/dsh-plugin-toolbox/</guid><description>DSH 才出来没几天，我已经往里装了九个插件。记一下它们各自补上了什么、怎么实现的，以及哪个最好使。</description><pubDate>Sun, 16 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-16T00:00:00.000Z</atom:updated><category>writing</category><category>technology</category><category>agent-systems</category><category>developer-productivity</category></item><item><title>dsh-skin-chatlab：给 DSH Web 做一套可扩展的聊天皮肤</title><link>https://liyuk.com/projects/2026/08/dsh-skin-chatlab/</link><guid isPermaLink="true">https://liyuk.com/projects/2026/08/dsh-skin-chatlab/</guid><description>用「基座 + 皮肤包」的架构，为 DSH Web GUI 做一个可开关、可卸载、不改任何现有插件的飞书风格聊天皮肤：工作区变项目组、会话变联系人、聊天变气泡。</description><pubDate>Sun, 16 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-16T00:00:00.000Z</atom:updated><category>project</category><category>technology</category><category>agent-systems</category><category>developer-productivity</category></item><item><title>技术规划，本质上是业务分析与竞品分析</title><link>https://liyuk.com/writing/2025/11/technical-planning-business-and-competitive-analysis/</link><guid isPermaLink="true">https://liyuk.com/writing/2025/11/technical-planning-business-and-competitive-analysis/</guid><description>技术规划不是项目清单，本质上是两件事：理解要服务的业务（业务分析），理解与对手的差距和水位（竞品分析），再把它们连成目标、取舍与执行之间的因果链。</description><pubDate>Mon, 10 Nov 2025 00:00:00 GMT</pubDate><atom:updated>2026-08-15T00:00:00.000Z</atom:updated><category>writing</category><category>technical-planning</category><category>engineering-management</category><category>strategy</category><category>decision-making</category><category>technology</category></item><item><title>商业模式画布：九个格子</title><link>https://liyuk.com/writing/2026/08/business-model-canvas/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/business-model-canvas/</guid><description>企业投资课上学的商业模式画布，记给自己：九个格子各是什么、各自要回答的那个问题，以及&quot;都满足才能做好项目&quot;这句话为什么要按企业阶段来看。</description><pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-15T00:00:00.000Z</atom:updated><category>writing</category><category>strategy</category><category>product-thinking</category><category>decision-making</category><category>learning</category></item><item><title>三个视角看一个项目：画布、路演、尽调</title><link>https://liyuk.com/writing/2026/08/canvas-pitch-diligence/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/canvas-pitch-diligence/</guid><description>记一个区分：商业模式画布是&quot;做给自己看&quot;，创业路演是&quot;讲给别人听&quot;，投资人尽调是&quot;别人来查你&quot;；三者的目的、重点和口径完全不同，别混着用。</description><pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-15T00:00:00.000Z</atom:updated><category>writing</category><category>strategy</category><category>product-thinking</category><category>decision-making</category><category>learning</category></item><item><title>管理复盘：从执行到系统的八个判断</title><link>https://liyuk.com/writing/2026/08/management-retrospective/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/management-retrospective/</guid><description>把过去几年在管理、协作与决策上反复出现的判断，收敛成一份只讲一次的总纲：判断、边界、对齐、上下文、闭环、资源、团队与复盘，每条各指向一篇展开。</description><pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-15T00:00:00.000Z</atom:updated><category>writing</category><category>management</category><category>leadership</category><category>decision-making</category><category>work-leadership</category></item><item><title>思维训练（四）：结构化思维实践</title><link>https://liyuk.com/writing/2026/08/structured-thinking-practice/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/structured-thinking-practice/</guid><description>五镜法的实战篇：用面试、晋升、汇报、项目合作四个场景，演示怎么把结构化工具和五镜套到真实问题上。</description><pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-15T00:00:00.000Z</atom:updated><category>writing</category><category>thinking</category><category>problem-framing</category><category>decision-making</category><category>communication</category><category>work-leadership</category></item><item><title>五镜法：联系导向的问题定位</title><link>https://liyuk.com/research/2026/08/connection-oriented-problem-location/</link><guid isPermaLink="true">https://liyuk.com/research/2026/08/connection-oriented-problem-location/</guid><description>一篇方法框架论文：把结构化思维从&quot;结论先行、不重不漏&quot;的通用表达，推进为&quot;结构化→发觉联系→推论底层问题→找到解决方案&quot;四阶段问题定位方法，以因果、二元、辩证、立场、利益五镜为核心透镜，给出可检验的训练协议与使用边界。</description><pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-15T00:00:00.000Z</atom:updated><category>research</category><category>thinking</category><category>problem-framing</category><category>decision-making</category><category>communication</category><category>leadership</category><category>work-leadership</category><category>strategy</category></item><item><title>未来五年中国二手住宅价格：一种可解释组合预测方法及其驻底分析（2026—2030）</title><link>https://liyuk.com/research/2026/08/housing-price-five-year-forecast/</link><guid isPermaLink="true">https://liyuk.com/research/2026/08/housing-price-five-year-forecast/</guid><description>基于 70 城官方二手指数（2019-2026，90 个月无缺口）提出可解释三成分组合预测（趋势延续/均值回归/季节性，权重由滚动样本外验证选择），给出全国与北京五年预测，并讨论驻底可能性。</description><pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-15T00:00:00.000Z</atom:updated><category>research</category><category>housing</category><category>forecasting</category><category>time-series</category><category>explainability</category><category>china</category></item><item><title>人的激励法则：情景激励模型</title><link>https://liyuk.com/research/2026/08/human-motivation-situational-model/</link><guid isPermaLink="true">https://liyuk.com/research/2026/08/human-motivation-situational-model/</guid><description>一篇理论综述、概念模型与应用框架：把激励从&quot;有没有动力&quot;重新定义为&quot;动机是否生成、能否转化为行为、能否维持&quot;的情境化过程，综合自我决定理论、期望-价值、目标设定、自我效能与行为模型，引入成长心理学、企业管理与组织员工心理学的视角，提出一个带&quot;成长轴&quot;的三层&quot;情景激励模型&quot;，并在职场中具象化为任务、目标、激励、反馈、发展通道与领导关系六个组件，落到投入、承诺、绩效、倦怠与离职等可测量结果上，并引入企业生命周期作为企业级调节变量，最终给出九条可证伪的激励法则。</description><pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-15T00:00:00.000Z</atom:updated><category>research</category><category>psychology</category><category>motivation</category><category>behavior</category><category>work-leadership</category><category>management</category></item><item><title>Neo Matrix</title><link>https://liyuk.com/projects/2026/08/neo-matrix/</link><guid isPermaLink="true">https://liyuk.com/projects/2026/08/neo-matrix/</guid><description>一个带个人供给方分成机制的 OpenAI 兼容中转平台：消费者通过统一入口调用模型，供给方托管闲置上游 Key，平台负责路由、计量、结算和提现。本文介绍项目、Mock 演示、商业模式、财务估算，以及上线前必须承担的风险与沉没成本。</description><pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-15T00:00:00.000Z</atom:updated><category>project</category><category>ai-relay</category><category>api-key</category><category>revenue-sharing</category><category>routing</category><category>settlement</category></item><item><title>OurBook · 我们眼中的大学</title><link>https://liyuk.com/projects/2026/08/ourbook/</link><guid isPermaLink="true">https://liyuk.com/projects/2026/08/ourbook/</guid><description>一个由南开毕业生发起的公益项目:在校生与毕业生写下自己真实的大学体验,帮高考生填报志愿时看到更立体的大学。到 2018 年项目已传承多年,内容托管在第三方平台;我在 2018 年重构项目、把数据接管回来自建站并一路留档——这篇文章也借它梳理了 2011-2026 高考资讯类产品的市场脉络。</description><pubDate>Sat, 19 May 2018 00:00:00 GMT</pubDate><atom:updated>2026-08-15T00:00:00.000Z</atom:updated><category>project</category><category>education</category><category>public-good</category><category>vuepress</category><category>static-site</category><category>community</category></item><item><title>Veylumi</title><link>https://liyuk.com/projects/2026/08/veylumi/</link><guid isPermaLink="true">https://liyuk.com/projects/2026/08/veylumi/</guid><description>一个面向中国与美国用户的 AI 美妆决策产品：从单张正脸照片到可解释的妆容建议、真实商品与教程。</description><pubDate>Thu, 13 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-15T00:00:00.000Z</atom:updated><category>project</category><category>product</category><category>ai</category><category>computer-vision</category><category>privacy</category><category>beauty</category></item><item><title>毛毛</title><link>https://liyuk.com/photos/maomao/</link><guid isPermaLink="true">https://liyuk.com/photos/maomao/</guid><description>家里的猫毛毛，坐在椅子上抬头，好奇地打量四周。</description><pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-15T00:00:00.000Z</atom:updated><category>gallery</category></item><item><title>网路上的虫子</title><link>https://liyuk.com/writing/2012/01/network-bug/</link><guid isPermaLink="true">https://liyuk.com/writing/2012/01/network-bug/</guid><description>一篇写于大学早期的科幻短篇：当二维网路中的虫子得到三维知识，它失去的不是无知，而是行动的能力。</description><pubDate>Sun, 01 Jan 2012 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>writing</category><category>fiction</category><category>archive</category><category>field-notes</category></item><item><title>面试题与工程师的成长路径</title><link>https://liyuk.com/writing/2018/04/interview-questions-archive/</link><guid isPermaLink="true">https://liyuk.com/writing/2018/04/interview-questions-archive/</guid><description>2018 年春季求职后整理的面试与工程基础资料索引；保留它，提醒自己面试题从来不只是面试题。</description><pubDate>Mon, 02 Apr 2018 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>writing</category><category>interview</category><category>engineering</category><category>archive</category><category>technology</category></item><item><title>产品启示录·一：从抱怨回到问题</title><link>https://liyuk.com/writing/2018/04/product-apocalypse-one/</link><guid isPermaLink="true">https://liyuk.com/writing/2018/04/product-apocalypse-one/</guid><description>一个双十一购物场景的旧案例：在急着想方案之前，先分辨用户真正遇到的是什么问题。</description><pubDate>Thu, 05 Apr 2018 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>writing</category><category>product</category><category>problem-framing</category><category>archive</category><category>work-leadership</category></item><item><title>前端入坑：幼儿园的车</title><link>https://liyuk.com/writing/2018/07/frontend-first-ride/</link><guid isPermaLink="true">https://liyuk.com/writing/2018/07/frontend-first-ride/</guid><description>一份写给前端初学者的旧路标：信息获取、学习记录、算法练习、面试与实习，都只是开始。</description><pubDate>Wed, 04 Jul 2018 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>writing</category><category>frontend</category><category>learning</category><category>career</category><category>archive</category><category>technology</category></item><item><title>技术知识库为什么需要入口页</title><link>https://liyuk.com/writing/2020/01/why-technical-knowledge-bases-need-entry-pages/</link><guid isPermaLink="true">https://liyuk.com/writing/2020/01/why-technical-knowledge-bases-need-entry-pages/</guid><description>入口页不是链接堆栈，而是不断变化的项目留给团队的共同记忆：它帮助读者按任务进入、判断信息是否仍有效，并找到负责维护的人。</description><pubDate>Mon, 06 Jan 2020 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>writing</category><category>technical-writing</category><category>knowledge-management</category><category>information-architecture</category><category>engineering</category><category>technology</category></item><item><title>文档不是记录，而是协作接口</title><link>https://liyuk.com/writing/2020/10/documents-are-collaboration-interfaces/</link><guid isPermaLink="true">https://liyuk.com/writing/2020/10/documents-are-collaboration-interfaces/</guid><description>一份技术文档的实用写法：先把结论和问题写清楚，再用合适的结构承接方案、进度与细节。</description><pubDate>Thu, 22 Oct 2020 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>writing</category><category>writing</category><category>technical-writing</category><category>communication</category><category>work-leadership</category></item><item><title>一次可复用的工程复盘，应该留下什么</title><link>https://liyuk.com/writing/2020/10/reusable-engineering-retrospective/</link><guid isPermaLink="true">https://liyuk.com/writing/2020/10/reusable-engineering-retrospective/</guid><description>工程复盘的价值不在于重述经过或追究个人，而在于把一次经历转化为能被验证、维护和复用的改进。</description><pubDate>Thu, 22 Oct 2020 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>writing</category><category>engineering</category><category>retrospective</category><category>learning</category><category>collaboration</category><category>technology</category></item><item><title>技术分享不是一场活动，而是一套知识协作方法</title><link>https://liyuk.com/writing/2020/10/what-good-technical-sharing-should-change/</link><guid isPermaLink="true">https://liyuk.com/writing/2020/10/what-good-technical-sharing-should-change/</guid><description>把技术分享从定期演讲，变成选题、研究、讨论与沉淀相互连接的知识协作系统。</description><pubDate>Thu, 22 Oct 2020 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>writing</category><category>technical-sharing</category><category>learning</category><category>knowledge-management</category><category>collaboration</category><category>technology</category></item><item><title>工程 POC 实战 FAQ：排期、同步、风险与交付</title><link>https://liyuk.com/writing/2021/04/engineering-poc-faq-responsibility-boundaries/</link><guid isPermaLink="true">https://liyuk.com/writing/2021/04/engineering-poc-faq-responsibility-boundaries/</guid><description>面对跨职能需求，工程 POC 应如何分工、同步风险、处理变更与控制自己的负荷？这是一份面向真实协作场景的公开 FAQ。</description><pubDate>Wed, 21 Apr 2021 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>writing</category><category>engineering</category><category>collaboration</category><category>project-management</category><category>risk-management</category><category>ownership</category><category>work-leadership</category></item><item><title>工程 POC：跨职能需求中的职责、边界与交付闭环</title><link>https://liyuk.com/writing/2021/08/requirement-poc-responsibilities/</link><guid isPermaLink="true">https://liyuk.com/writing/2021/08/requirement-poc-responsibilities/</guid><description>工程 POC 不是项目秘书，也不是替所有人兜底；它的职责是让目标、承诺、风险和决策在跨职能协作中保持清楚。</description><pubDate>Tue, 17 Aug 2021 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>writing</category><category>project-management</category><category>engineering</category><category>collaboration</category><category>ownership</category><category>delivery</category><category>work-leadership</category></item><item><title>如何写一份产品概览，而不把资料堆成百科</title><link>https://liyuk.com/writing/2021/09/product-overview-is-a-decision-model/</link><guid isPermaLink="true">https://liyuk.com/writing/2021/09/product-overview-is-a-decision-model/</guid><description>产品概览的职责不是收集尽可能多的事实，而是帮助读者在有限时间内建立共同问题、形成判断，并知道还缺什么证据。</description><pubDate>Wed, 15 Sep 2021 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>writing</category><category>product-thinking</category><category>writing</category><category>research</category><category>collaboration</category><category>work-leadership</category></item><item><title>从零搭团队时，先设计什么</title><link>https://liyuk.com/writing/2023/06/from-zero-design-the-team/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/06/from-zero-design-the-team/</guid><description>当既有梯队失效或需要重新开始时，先重建责任、标准和培养机制，而不只是重画一张分工图。</description><pubDate>Thu, 01 Jun 2023 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>writing</category><category>leadership</category><category>collaboration</category><category>management</category><category>work-leadership</category></item><item><title>职场发展问题：晋升与面试前的完整自查清单</title><link>https://liyuk.com/writing/2023/08/career-growth-ten-questions/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/08/career-growth-ten-questions/</guid><description>一份不压缩的问题库：围绕业务、技术、团队、个人判断与组织能力，逐项准备晋升材料、面试回答和阶段复盘。</description><pubDate>Tue, 01 Aug 2023 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>writing</category><category>career</category><category>promotion</category><category>interview</category><category>leadership</category><category>engineering</category><category>work-leadership</category></item><item><title>新的开始</title><link>https://liyuk.com/writing/2026/08/rebuilding-this-site/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/rebuilding-this-site/</guid><description>这个站点正在从旧的静态博客，迁移为一个关于技术、工作与生活观察的个人出版物；也记录这次重建时做出的取舍。</description><pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>writing</category><category>site-notes</category><category>field-notes</category></item><item><title>从零搭建一个回国代理：VLESS + Reality 的踩坑记录</title><link>https://liyuk.com/writing/2026/08/vless-reality-return-proxy-notes/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/08/vless-reality-return-proxy-notes/</guid><description>从 SSH 临时直连，到要照顾手机和家人的使用体验，最后用 sing-box 收敛为一套可维护的回国网络方案。</description><pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>writing</category><category>sing-box</category><category>vless</category><category>reality</category><category>network</category><category>operations</category><category>technology</category></item><item><title>把 AI 能力放进工程组织前，先定义哪些边界</title><link>https://liyuk.com/research/2026/08/ai-engineering-capability-boundaries/</link><guid isPermaLink="true">https://liyuk.com/research/2026/08/ai-engineering-capability-boundaries/</guid><description>一篇立场论文：基于作者在真实工程组织推进 AI 基建与试点的经验，提出上下文、职责、授权、度量四类边界，并给出可否证的试点协议与一个最小 harness 落地示范。</description><pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>research</category><category>ai</category><category>software-engineering</category><category>agent-systems</category><category>developer-productivity</category><category>governance</category><category>technology</category></item><item><title>数据度量作为组织协议：口径、测量、分级与复盘</title><link>https://liyuk.com/research/2026/08/data-measurement-organizational-protocol/</link><guid isPermaLink="true">https://liyuk.com/research/2026/08/data-measurement-organizational-protocol/</guid><description>一篇研究设计与协议论文：把数据度量从&quot;看板上放什么&quot;重构为可复算、可复核、能支持决策的协作协议，给出口径定义、测量单位、指标分级、字典与复盘的最小机制。</description><pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>research</category><category>data</category><category>metrics</category><category>measurement</category><category>collaboration</category><category>reproducibility</category><category>technology</category></item><item><title>开发者生产力不是工具目录，而是一个反馈系统</title><link>https://liyuk.com/research/2026/08/developer-productivity-feedback-loops/</link><guid isPermaLink="true">https://liyuk.com/research/2026/08/developer-productivity-feedback-loops/</guid><description>一篇研究综述与立场论文：把工程生产力定义为持续缩短的&quot;提出改变—获得可信反馈—安全修正&quot;回路，并给出度量、默认路径与可证伪的试点协议。</description><pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>research</category><category>developer-productivity</category><category>platform-engineering</category><category>feedback-loops</category><category>software-engineering</category><category>technology</category></item><item><title>当 AI 降低工作流壁垒，职能线与业务线怎样重新划分</title><link>https://liyuk.com/research/2026/08/functional-lines-versus-business-lines/</link><guid isPermaLink="true">https://liyuk.com/research/2026/08/functional-lines-versus-business-lines/</guid><description>一篇立场论文：职能线曾在高度分工时高效；当工具降低技能壁垒后，组织应围绕全链路业务能力重新设计。给出机制、组织形态谱系、判断信号、中美两种起点、人才需求与可否证的试点协议。</description><pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>research</category><category>organization-design</category><category>ai</category><category>engineering</category><category>functional-teams</category><category>business-lines</category><category>work-leadership</category></item><item><title>人际风险分析协议：从关系材料到事实、假设与行动</title><link>https://liyuk.com/research/2026/08/relationship-material-analysis-m1-m5/</link><guid isPermaLink="true">https://liyuk.com/research/2026/08/relationship-material-analysis-m1-m5/</guid><description>一篇研究设计与协议论文：提出一套以安全行动为目标、覆盖亲密与一般人际关系的材料组织与风险标注协议，并界定 AI 的结构化副驾驶位置。</description><pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>research</category><category>relationships</category><category>interpersonal-analysis</category><category>anti-scam</category><category>psychology</category><category>human-ai-collaboration</category><category>work-leadership</category></item><item><title>职场关系分析协议：权力、权责与结构位置</title><link>https://liyuk.com/research/2026/08/workplace-relationship-analysis-protocol/</link><guid isPermaLink="true">https://liyuk.com/research/2026/08/workplace-relationship-analysis-protocol/</guid><description>一篇研究设计与协议论文：提出一套以可核验信号为目标、面向职场场景的材料组织与工作关系分析协议，覆盖上中下三层级的工作安全、权力结构、横向竞争、权责错位、职业安全、职业发展与职业心理健康。</description><pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>research</category><category>workplace</category><category>power</category><category>professional-relationships</category><category>risk-analysis</category><category>human-ai-collaboration</category><category>work-leadership</category></item><item><title>Coding Agent Harness Study（一）：架构比较与受限文件执行</title><link>https://liyuk.com/projects/2026/08/claude-code-harness-study/</link><guid isPermaLink="true">https://liyuk.com/projects/2026/08/claude-code-harness-study/</guid><description>从公开资料、可观察行为与可运行的微内核出发，学习怎样把 coding agent 的权限、工具调用和运行轨迹变成可验证的系统边界。</description><pubDate>Thu, 13 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>project</category><category>agent</category><category>coding-agent</category><category>systems</category><category>typescript</category></item><item><title>可测量与不可测量：中国房价数据的一种来源—口径感知构建方法（以北京为区级案例）</title><link>https://liyuk.com/research/2026/08/china-housing-price-data-methods/</link><guid isPermaLink="true">https://liyuk.com/research/2026/08/china-housing-price-data-methods/</guid><description>基于一套已补全的中国房价数据资产（70 城官方指数面板、全国宏观面板与 LPR 序列、北京区级挂牌均价月度序列、官方区级网签与年度交易），提出来源—口径感知的数据构建框架，并给出跨口径实证。</description><pubDate>Sat, 08 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-08T00:00:00.000Z</atom:updated><category>research</category><category>data</category><category>machine-learning</category><category>housing</category><category>reproducibility</category><category>provenance</category></item><item><title>从提示词到叙事生产：CanonLoom 0.2.0 的可审计长篇小说人机协作架构</title><link>https://liyuk.com/research/2026/08/canonloom-auditable-narrative-production/</link><guid isPermaLink="true">https://liyuk.com/research/2026/08/canonloom-auditable-narrative-production/</guid><description>一篇系统设计论文：将长篇小说协作建模为可恢复、可审计且由作者批准的状态转换，并给出不把机械分数误认为文学价值的评估方案。</description><pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-03T00:00:00.000Z</atom:updated><category>research</category><category>human-ai-collaboration</category><category>agent-systems</category><category>narrative</category><category>auditability</category><category>technology</category></item><item><title>CanonLoom</title><link>https://liyuk.com/projects/2026/08/canonloom/</link><guid isPermaLink="true">https://liyuk.com/projects/2026/08/canonloom/</guid><description>一个命令驱动的长篇小说生产工作流：作者用短命令驱动，Agent 负责创作，Python 做确定性校验，作者在每个关键节点做选择和批准。</description><pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-03T00:00:00.000Z</atom:updated><category>project</category><category>agent</category><category>creative-writing</category><category>workflow</category><category>python</category></item><item><title>Departure Under Sunlit Flames</title><link>https://liyuk.com/writing/2026/05/departure-under-sunlit-flames/</link><guid isPermaLink="true">https://liyuk.com/writing/2026/05/departure-under-sunlit-flames/</guid><description>一段八年半职业旅途结束时的告别、回望与感谢。</description><pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate><atom:updated>2026-05-29T00:00:00.000Z</atom:updated><category>writing</category><category>career</category><category>reflection</category><category>leadership</category><category>work-leadership</category></item><item><title>把口语想法写成可决策的文档</title><link>https://liyuk.com/writing/2025/12/turn-spoken-ideas-into-decision-documents/</link><guid isPermaLink="true">https://liyuk.com/writing/2025/12/turn-spoken-ideas-into-decision-documents/</guid><description>把散乱想法蒸馏成一篇能讨论、能落地的文档：工具负责整理，人负责判断。</description><pubDate>Wed, 31 Dec 2025 00:00:00 GMT</pubDate><atom:updated>2025-12-31T00:00:00.000Z</atom:updated><category>writing</category><category>writing</category><category>decision-making</category><category>communication</category><category>work-leadership</category></item><item><title>思维训练（二）：数数游戏——如何把模糊表达变成清楚的问题</title><link>https://liyuk.com/writing/2025/08/counting-practice/</link><guid isPermaLink="true">https://liyuk.com/writing/2025/08/counting-practice/</guid><description>从说清 1、2、3 开始，练习倾听、复述、回答与自我复盘，让混乱的信息获得可以行动的结构。</description><pubDate>Wed, 20 Aug 2025 00:00:00 GMT</pubDate><atom:updated>2025-08-20T00:00:00.000Z</atom:updated><category>writing</category><category>thinking</category><category>communication</category><category>self-reflection</category><category>work-leadership</category></item><item><title>一套日常全妆的八步流程</title><link>https://liyuk.com/writing/2025/04/everyday-full-makeup-decision-framework/</link><guid isPermaLink="true">https://liyuk.com/writing/2025/04/everyday-full-makeup-decision-framework/</guid><description>从妆前准备到妆容收尾，一套偏自然、注重持妆与骨相修饰的全妆实操顺序。</description><pubDate>Sat, 12 Apr 2025 00:00:00 GMT</pubDate><atom:updated>2025-04-12T00:00:00.000Z</atom:updated><category>writing</category><category>beauty</category><category>everyday-life</category><category>guide</category><category>field-notes</category></item><item><title>从肤色观察到产品选择</title><link>https://liyuk.com/writing/2025/04/from-skin-observation-to-product-selection/</link><guid isPermaLink="true">https://liyuk.com/writing/2025/04/from-skin-observation-to-product-selection/</guid><description>选彩妆不必先背色号或品牌：先在自然光下观察肤色、明度与当天的肤感，再把选择缩小到适合自己的颜色和质地。</description><pubDate>Sat, 12 Apr 2025 00:00:00 GMT</pubDate><atom:updated>2025-04-12T00:00:00.000Z</atom:updated><category>writing</category><category>beauty</category><category>everyday-life</category><category>guide</category><category>skincare</category><category>field-notes</category></item><item><title>招聘与职业关系（二）：推荐不是转发职位</title><link>https://liyuk.com/writing/2025/03/referral-is-mutual-recognition/</link><guid isPermaLink="true">https://liyuk.com/writing/2025/03/referral-is-mutual-recognition/</guid><description>一次负责任的推荐，不是促成一次投递，而是帮助双方获得足够真实的信息，判断是否值得继续靠近。</description><pubDate>Sat, 01 Mar 2025 00:00:00 GMT</pubDate><atom:updated>2025-03-01T00:00:00.000Z</atom:updated><category>writing</category><category>communication</category><category>relationships</category><category>career</category><category>team</category><category>work-leadership</category></item><item><title>送礼不是选商品：一套理解关系的提问框架</title><link>https://liyuk.com/writing/2025/02/gifting-question-framework/</link><guid isPermaLink="true">https://liyuk.com/writing/2025/02/gifting-question-framework/</guid><description>一份可直接使用的送礼操作指南：先确认人和场景，再从通用、定制、体验三类礼物里缩小选择。</description><pubDate>Thu, 20 Feb 2025 00:00:00 GMT</pubDate><atom:updated>2025-02-20T00:00:00.000Z</atom:updated><category>writing</category><category>relationships</category><category>gifts</category><category>everyday-life</category><category>guide</category><category>field-notes</category></item><item><title>招聘 Branding：建立&quot;我们能一起做成&quot;的共同相信</title><link>https://liyuk.com/writing/2024/05/recruiting-brand-is-a-trust-system/</link><guid isPermaLink="true">https://liyuk.com/writing/2024/05/recruiting-brand-is-a-trust-system/</guid><description>招聘品牌不是美化职位，而是把一件事讲清楚：它为什么重要、团队凭什么可能做成、加入的人会具体做什么。</description><pubDate>Mon, 20 May 2024 00:00:00 GMT</pubDate><atom:updated>2024-05-20T00:00:00.000Z</atom:updated><category>writing</category><category>hiring</category><category>leadership</category><category>communication</category><category>team-building</category><category>work-leadership</category></item><item><title>思维训练（一）：Top K 问题——先找到最重要的事</title><link>https://liyuk.com/writing/2024/02/top-k-thinking/</link><guid isPermaLink="true">https://liyuk.com/writing/2024/02/top-k-thinking/</guid><description>面对一长串任务、问题和观点时，先定义判断口径，再找出真正排在前面的那几件事。</description><pubDate>Fri, 09 Feb 2024 00:00:00 GMT</pubDate><atom:updated>2024-02-09T00:00:00.000Z</atom:updated><category>writing</category><category>thinking</category><category>prioritization</category><category>communication</category><category>work-leadership</category></item><item><title>不安全感、比较与长期能力：把不安聊成可行动的方向</title><link>https://liyuk.com/writing/2024/01/insecurity-comparison-and-long-term-capability/</link><guid isPermaLink="true">https://liyuk.com/writing/2024/01/insecurity-comparison-and-long-term-capability/</guid><description>不安全感来自环境，也来自比较。先分清来源，再调整预期、拉长时间尺度，把注意力从&quot;别人怎么样&quot;拉回&quot;我该练什么&quot;。</description><pubDate>Sat, 20 Jan 2024 00:00:00 GMT</pubDate><atom:updated>2024-01-20T00:00:00.000Z</atom:updated><category>writing</category><category>self-reflection</category><category>growth</category><category>communication</category><category>work-leadership</category></item><item><title>业务增长放缓：把焦虑聊成&quot;先定基调，再解决关键路径&quot;</title><link>https://liyuk.com/writing/2023/12/anxiety-when-growth-slows/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/12/anxiety-when-growth-slows/</guid><description>业务增速放缓时，团队会集体焦虑。先定&quot;积极应对、分析问题、解决关键路径&quot;的基调，再逐项聊清楚问题出在哪。</description><pubDate>Sun, 10 Dec 2023 00:00:00 GMT</pubDate><atom:updated>2023-12-10T00:00:00.000Z</atom:updated><category>writing</category><category>self-reflection</category><category>communication</category><category>decision-making</category><category>work-leadership</category></item><item><title>我的读书档案：书单、工具与阅读笔记</title><link>https://liyuk.com/writing/2023/11/my-reading-archives/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/11/my-reading-archives/</guid><description>从 2021 到 2023 年的一份个人阅读记录：读什么、怎样记，以及一些还没有想明白的读后感。</description><pubDate>Tue, 14 Nov 2023 00:00:00 GMT</pubDate><atom:updated>2023-11-14T00:00:00.000Z</atom:updated><category>writing</category><category>reading</category><category>books</category><category>notes</category><category>learning</category><category>archive</category><category>field-notes</category></item><item><title>前端工程师如何从执行走向系统判断</title><link>https://liyuk.com/writing/2023/08/frontend-engineer-system-judgment/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/08/frontend-engineer-system-judgment/</guid><description>职业发展不只是把更多需求做出来，而是逐步扩大问题定义、取舍和协作的责任范围。</description><pubDate>Tue, 01 Aug 2023 00:00:00 GMT</pubDate><atom:updated>2023-08-01T00:00:00.000Z</atom:updated><category>writing</category><category>frontend</category><category>career-development</category><category>systems-thinking</category><category>decision-making</category><category>work-leadership</category></item><item><title>目标、规划与复盘：把&quot;交作业&quot;变成自己的成长</title><link>https://liyuk.com/writing/2023/07/goals-retrospectives-and-next-actions/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/07/goals-retrospectives-and-next-actions/</guid><description>规划和复盘不是为了完成任务。从制定目标的困难、到复盘的方法、再到以自我成长为导向，一套完整的话题清单。</description><pubDate>Sun, 16 Jul 2023 00:00:00 GMT</pubDate><atom:updated>2023-07-16T00:00:00.000Z</atom:updated><category>writing</category><category>retrospective</category><category>decision-making</category><category>growth</category><category>work-leadership</category></item><item><title>东京漫游</title><link>https://liyuk.com/writing/2023/06/tokyo-wandering/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/06/tokyo-wandering/</guid><description>2023 年 6 月六天：银座、涉谷、横滨、镰仓，以及密度、步行和&quot;面积为什么要单独算钱&quot;。</description><pubDate>Sun, 11 Jun 2023 00:00:00 GMT</pubDate><atom:updated>2023-06-11T00:00:00.000Z</atom:updated><category>writing</category><category>japan</category><category>tokyo</category><category>travel</category><category>field-notes</category></item><item><title>如何设计新人、骨干与负责人三条成长路径</title><link>https://liyuk.com/writing/2023/06/growth-paths-for-newcomers-core-and-leads/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/06/growth-paths-for-newcomers-core-and-leads/</guid><description>成长路径不是职级清单，而是三种不断扩大的责任：完成任务、经营问题，以及让他人也能完成重要工作。</description><pubDate>Thu, 01 Jun 2023 00:00:00 GMT</pubDate><atom:updated>2023-06-01T00:00:00.000Z</atom:updated><category>writing</category><category>career</category><category>growth</category><category>team</category><category>leadership</category><category>work-leadership</category></item><item><title>自我迭代不是鸡血，而是一套反馈系统</title><link>https://liyuk.com/writing/2023/06/self-iteration-feedback-system/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/06/self-iteration-feedback-system/</guid><description>所谓自我迭代，不是无止境地逼自己更快，而是看清目标、观察结果、调整行动，并在不确定中持续校准。</description><pubDate>Thu, 01 Jun 2023 00:00:00 GMT</pubDate><atom:updated>2023-06-01T00:00:00.000Z</atom:updated><category>writing</category><category>growth</category><category>self-reflection</category><category>feedback</category><category>work-leadership</category></item><item><title>培养不是培训：团队能力如何复利</title><link>https://liyuk.com/writing/2023/06/team-development-compounds/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/06/team-development-compounds/</guid><description>团队培养的目的不是把经验灌输给每个人，而是让判断、协作与责任能够被练习、反馈和传递。</description><pubDate>Thu, 01 Jun 2023 00:00:00 GMT</pubDate><atom:updated>2023-06-01T00:00:00.000Z</atom:updated><category>writing</category><category>team</category><category>leadership</category><category>growth</category><category>mentoring</category><category>work-leadership</category></item><item><title>西海岸日常</title><link>https://liyuk.com/writing/2023/05/west-coast-daily-life/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/05/west-coast-daily-life/</guid><description>2023 年 5 月的十五天：一边在另一个时区工作，一边开车、加油、停车、算账。最深的印象不是景点，是时差和&quot;贵&quot;。</description><pubDate>Mon, 15 May 2023 00:00:00 GMT</pubDate><atom:updated>2023-05-15T00:00:00.000Z</atom:updated><category>writing</category><category>united-states</category><category>west-coast</category><category>travel</category><category>field-notes</category></item><item><title>思维训练（三）：如何给自己提出好的问题</title><link>https://liyuk.com/writing/2023/04/how-to-ask-yourself-better-questions/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/04/how-to-ask-yourself-better-questions/</guid><description>好问题不是聪明的发问，而是把模糊的不适感转成可核验、可讨论、可行动的对象；这是一套用于工作、学习与复盘的日常练习。</description><pubDate>Wed, 12 Apr 2023 00:00:00 GMT</pubDate><atom:updated>2023-04-12T00:00:00.000Z</atom:updated><category>writing</category><category>thinking</category><category>learning</category><category>reflection</category><category>problem-solving</category><category>work-leadership</category></item><item><title>协作重叠不是忙碌：怎样区分健康冗余与有害 overlap</title><link>https://liyuk.com/writing/2023/04/healthy-redundancy-and-harmful-overlap/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/04/healthy-redundancy-and-harmful-overlap/</guid><description>容灾和复核是健康冗余；抢资源、抢项目和不清楚的授权导致的赛马，则会把组织推入零和疲惫。</description><pubDate>Mon, 10 Apr 2023 00:00:00 GMT</pubDate><atom:updated>2023-04-10T00:00:00.000Z</atom:updated><category>writing</category><category>collaboration</category><category>organization</category><category>management</category><category>work-leadership</category></item><item><title>资源充足时，为什么组织仍会变慢</title><link>https://liyuk.com/writing/2023/04/escaping-the-resource-curse/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/04/escaping-the-resource-curse/</guid><description>资源诅咒不是钱或人太多，而是资源让目标更细、结构更重、低质量决策更多，最终失去发现并解决高 ROI 问题的能力。</description><pubDate>Sun, 09 Apr 2023 00:00:00 GMT</pubDate><atom:updated>2023-04-09T00:00:00.000Z</atom:updated><category>writing</category><category>organization</category><category>decision-making</category><category>prioritization</category><category>work-leadership</category></item><item><title>焦虑与压力：在不安里聊出可行动的工作边界</title><link>https://liyuk.com/writing/2023/04/anxiety-and-work-boundaries/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/04/anxiety-and-work-boundaries/</guid><description>工作中的一对一不是心理咨询。把焦虑拆成&quot;能控制的和不能控制的&quot;，先聊认知，再聊具体压力与工作条件。</description><pubDate>Sat, 08 Apr 2023 00:00:00 GMT</pubDate><atom:updated>2023-04-08T00:00:00.000Z</atom:updated><category>writing</category><category>communication</category><category>self-reflection</category><category>collaboration</category><category>work-leadership</category></item><item><title>AI 加速之后，职能线与业务线怎样重新划分</title><link>https://liyuk.com/writing/2023/04/functional-teams-in-the-ai-era/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/04/functional-teams-in-the-ai-era/</guid><description>职能线曾帮助专业能力高效运转；当工具降低工作流壁垒后，组织更应围绕全链路业务能力重新设计，而不是固守历史分工。</description><pubDate>Thu, 06 Apr 2023 00:00:00 GMT</pubDate><atom:updated>2023-04-06T00:00:00.000Z</atom:updated><category>writing</category><category>organization-design</category><category>ai</category><category>engineering</category><category>work-leadership</category></item><item><title>组织变化发生时，怎样同步才不制造猜测</title><link>https://liyuk.com/writing/2023/04/communicating-organizational-change/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/04/communicating-organizational-change/</guid><description>先同步已经官方确认的客观事实，不掩盖问题；再分别对上、对下和协作者说明目标、稳定性与新的协作方式。</description><pubDate>Tue, 04 Apr 2023 00:00:00 GMT</pubDate><atom:updated>2023-04-04T00:00:00.000Z</atom:updated><category>writing</category><category>management</category><category>communication</category><category>organizational-change</category><category>work-leadership</category></item><item><title>人力规划不是比率游戏：从资源出现时开始对齐</title><link>https://liyuk.com/writing/2023/04/headcount-is-not-a-ratio/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/04/headcount-is-not-a-ratio/</guid><description>人力配比只是动态概念。更重要的是在扩张、收缩和方案变化时，把目标、市场与资源约束及时对齐。</description><pubDate>Sun, 02 Apr 2023 00:00:00 GMT</pubDate><atom:updated>2023-04-02T00:00:00.000Z</atom:updated><category>writing</category><category>planning</category><category>management</category><category>capacity-planning</category><category>work-leadership</category></item><item><title>1-on-1 不是例会：信息、预期与决策权怎样对齐</title><link>https://liyuk.com/writing/2023/03/one-on-ones-and-decision-rights/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/03/one-on-ones-and-decision-rights/</guid><description>1-on-1 的核心是让上下级了解彼此目标与诉求；授权必须随着信息和角色边界发生，而不是把上下文误当作决策权转移。</description><pubDate>Fri, 31 Mar 2023 00:00:00 GMT</pubDate><atom:updated>2023-03-31T00:00:00.000Z</atom:updated><category>writing</category><category>management</category><category>communication</category><category>ownership</category><category>work-leadership</category></item><item><title>共享核心与本地变化：多地区系统怎样演进</title><link>https://liyuk.com/writing/2023/03/shared-core-and-local-variation/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/03/shared-core-and-local-variation/</guid><description>多地区系统既不能把所有差异硬塞进一个核心，也不能让每个地区重复建设。关键是识别稳定边界、保留扩展点，并明确模块所有权。</description><pubDate>Wed, 29 Mar 2023 00:00:00 GMT</pubDate><atom:updated>2023-03-29T00:00:00.000Z</atom:updated><category>writing</category><category>architecture</category><category>engineering</category><category>systems-design</category><category>technology</category></item><item><title>信息同步不是抄送：怎样让对方能作决定</title><link>https://liyuk.com/writing/2023/03/information-sync-for-decisions/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/03/information-sync-for-decisions/</guid><description>有效同步的目标不是把知道的一切都发出去，而是让特定读者在适当时间获得足以判断、协作或行动的信息。</description><pubDate>Mon, 27 Mar 2023 00:00:00 GMT</pubDate><atom:updated>2023-03-27T00:00:00.000Z</atom:updated><category>writing</category><category>communication</category><category>documentation</category><category>collaboration</category><category>work-leadership</category></item><item><title>分布式团队如何减少上下文损耗</title><link>https://liyuk.com/writing/2023/03/reducing-context-loss-in-distributed-teams/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/03/reducing-context-loss-in-distributed-teams/</guid><description>异地协作最贵的成本往往不是时差，而是上下文反复丢失。清楚的闭环责任、异步文档和有限的重叠时间能让协作更稳。</description><pubDate>Sat, 25 Mar 2023 00:00:00 GMT</pubDate><atom:updated>2023-03-25T00:00:00.000Z</atom:updated><category>writing</category><category>distributed-work</category><category>collaboration</category><category>communication</category><category>work-leadership</category></item><item><title>资源不足时，怎样不让团队靠透支运转</title><link>https://liyuk.com/writing/2023/03/working-under-resource-constraints/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/03/working-under-resource-constraints/</guid><description>资源紧张不是一句&quot;大家再努力一点&quot;能解决的问题。团队需要把承诺、风险和投诉还原为事实，并公开作出取舍。</description><pubDate>Thu, 23 Mar 2023 00:00:00 GMT</pubDate><atom:updated>2023-03-23T00:00:00.000Z</atom:updated><category>writing</category><category>capacity-planning</category><category>management</category><category>prioritization</category><category>delivery</category><category>work-leadership</category></item><item><title>「一定不做」不是懒惰：给承诺设边界</title><link>https://liyuk.com/writing/2023/03/defining-what-not-to-do/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/03/defining-what-not-to-do/</guid><description>时间管理的核心不是塞满日历，而是根据角色、价值和机会成本明确承诺，也明确哪些事情此刻不做。</description><pubDate>Tue, 21 Mar 2023 00:00:00 GMT</pubDate><atom:updated>2023-03-21T00:00:00.000Z</atom:updated><category>writing</category><category>prioritization</category><category>time-management</category><category>leadership</category><category>work-leadership</category></item><item><title>项目合作发生冲突时，先对齐哪三件事</title><link>https://liyuk.com/writing/2023/03/resolving-project-conflicts/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/03/resolving-project-conflicts/</guid><description>多数项目冲突不是谁不配合，而是目标、事实或决策权没有被明确。先把这三件事说清，才能让分歧回到可解决的对象上。</description><pubDate>Sun, 19 Mar 2023 00:00:00 GMT</pubDate><atom:updated>2023-03-19T00:00:00.000Z</atom:updated><category>writing</category><category>project-management</category><category>collaboration</category><category>communication</category><category>work-leadership</category></item><item><title>质量不是某个团队的任务：共同为交付结果负责</title><link>https://liyuk.com/writing/2023/03/quality-is-shared-accountability/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/03/quality-is-shared-accountability/</guid><description>每个角色对自己的交付负责，也共同对线上结果负责。质量闭环的关键是监控、快速止损、精确修复与复盘。</description><pubDate>Fri, 17 Mar 2023 00:00:00 GMT</pubDate><atom:updated>2023-03-17T00:00:00.000Z</atom:updated><category>writing</category><category>quality</category><category>reliability</category><category>engineering</category><category>technology</category></item><item><title>产研关系不是&quot;配合&quot;：先站到同一个阵营</title><link>https://liyuk.com/writing/2023/03/product-engineering-trust/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/03/product-engineering-trust/</guid><description>好合作建立在信任、信息互通和共同解决问题上；目标冲突时不要私自承诺，而要带着完整信息上升对齐。</description><pubDate>Wed, 15 Mar 2023 00:00:00 GMT</pubDate><atom:updated>2023-03-15T00:00:00.000Z</atom:updated><category>writing</category><category>collaboration</category><category>trust</category><category>product-thinking</category><category>work-leadership</category></item><item><title>工程规范怎样既减少返工，也不制造官僚流程</title><link>https://liyuk.com/writing/2023/03/engineering-standards-without-bureaucracy/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/03/engineering-standards-without-bureaucracy/</guid><description>好规范不是把每一步都变成审批，而是让最容易失真、返工和出事故的关键交接点变得可见、可讨论、可复用。</description><pubDate>Mon, 13 Mar 2023 00:00:00 GMT</pubDate><atom:updated>2023-03-13T00:00:00.000Z</atom:updated><category>writing</category><category>engineering</category><category>process</category><category>collaboration</category><category>technology</category></item><item><title>当一个人失去动力，管理者能做什么</title><link>https://liyuk.com/writing/2023/03/when-a-team-member-loses-motivation/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/03/when-a-team-member-loses-motivation/</guid><description>动力不是靠口号或压力制造的。管理者能做的是分辨问题来自环境、角色、回报还是个人状态，并提供诚实而有限的支持。</description><pubDate>Sat, 11 Mar 2023 00:00:00 GMT</pubDate><atom:updated>2023-03-11T00:00:00.000Z</atom:updated><category>writing</category><category>management</category><category>team</category><category>growth</category><category>work-leadership</category></item><item><title>管理者离代码多远才合适</title><link>https://liyuk.com/writing/2023/03/how-close-managers-should-stay-to-code/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/03/how-close-managers-should-stay-to-code/</guid><description>管理者离代码的距离不该是固定的，而应由目标决定：近到能看懂架构、风险和阻塞，远到把力气花在定义问题、打通协作、向上拿权限上。</description><pubDate>Thu, 09 Mar 2023 00:00:00 GMT</pubDate><atom:updated>2023-03-09T00:00:00.000Z</atom:updated><category>writing</category><category>engineering-management</category><category>leadership</category><category>engineering</category><category>work-leadership</category></item><item><title>代码为什么会变坏：从局部便利到系统债务</title><link>https://liyuk.com/writing/2023/03/why-code-decays/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/03/why-code-decays/</guid><description>代码劣化并不主要来自某一次&quot;写得差&quot;，而来自局部变更不断绕过共同边界；真正要维护的是设计与协作的一致性。</description><pubDate>Tue, 07 Mar 2023 00:00:00 GMT</pubDate><atom:updated>2023-03-07T00:00:00.000Z</atom:updated><category>writing</category><category>engineering</category><category>code-quality</category><category>architecture</category><category>technology</category></item><item><title>当团队说不清独特价值时，工程师还能做什么</title><link>https://liyuk.com/writing/2023/03/engineering-without-unique-value/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/03/engineering-without-unique-value/</guid><description>技术不能凭空制造卖点，但工程师仍能帮助团队更准确地理解用户、缩短验证周期，并把隐含的约束变成可选择的问题。</description><pubDate>Sun, 05 Mar 2023 00:00:00 GMT</pubDate><atom:updated>2023-03-05T00:00:00.000Z</atom:updated><category>writing</category><category>engineering</category><category>product-thinking</category><category>decision-making</category><category>work-leadership</category></item><item><title>陌生领域的第一张地图：怎样理解一条完整价值链</title><link>https://liyuk.com/writing/2023/03/mapping-an-unfamiliar-value-chain/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/03/mapping-an-unfamiliar-value-chain/</guid><description>进入陌生业务或系统时，不要急着从局部方案开始。先画出使用者、流程、输入输出、关键约束和价值，才能知道该问什么。</description><pubDate>Fri, 03 Mar 2023 00:00:00 GMT</pubDate><atom:updated>2023-03-03T00:00:00.000Z</atom:updated><category>writing</category><category>product-thinking</category><category>learning</category><category>systems-thinking</category><category>work-leadership</category></item><item><title>一线技术管理的三种产出</title><link>https://liyuk.com/writing/2023/03/frontline-engineering-management/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/03/frontline-engineering-management/</guid><description>一线管理不是替团队多做一点事，而是持续产出更好的判断、可预期的交付，以及能自我修复的协作系统。</description><pubDate>Wed, 01 Mar 2023 00:00:00 GMT</pubDate><atom:updated>2023-03-01T00:00:00.000Z</atom:updated><category>writing</category><category>technical-management</category><category>leadership</category><category>decision-making</category><category>team</category><category>work-leadership</category></item><item><title>印尼十四日记</title><link>https://liyuk.com/writing/2023/02/indonesia-fourteen-days/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/02/indonesia-fourteen-days/</guid><description>2023 年 2 月在雅加达的十四天：一座被折叠、被切开的城市，高楼和路边摊各自过着各自的日常。</description><pubDate>Mon, 20 Feb 2023 00:00:00 GMT</pubDate><atom:updated>2023-02-20T00:00:00.000Z</atom:updated><category>writing</category><category>indonesia</category><category>jakarta</category><category>travel</category><category>field-notes</category></item><item><title>评估潜力时，我们真正该看什么</title><link>https://liyuk.com/writing/2023/02/evaluating-potential-with-care/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/02/evaluating-potential-with-care/</guid><description>潜力不是履历或一次表现的标签。比起判断一个人“够不够聪明”，不如观察他怎样学习、行动、思考，以及从挫折中恢复。</description><pubDate>Wed, 15 Feb 2023 00:00:00 GMT</pubDate><atom:updated>2023-02-15T00:00:00.000Z</atom:updated><category>writing</category><category>growth</category><category>judgment</category><category>learning</category><category>self-reflection</category><category>work-leadership</category></item><item><title>如何做好沟通：从&quot;不知道聊什么&quot;到把话聊明白</title><link>https://liyuk.com/writing/2023/01/clarify-feedback-and-commitment/</link><guid isPermaLink="true">https://liyuk.com/writing/2023/01/clarify-feedback-and-commitment/</guid><description>沟通的话题很大，但可以很具体。从&quot;先澄清再反馈最后承诺&quot;讲起，附一套工作沟通的完整问题清单。</description><pubDate>Sat, 14 Jan 2023 00:00:00 GMT</pubDate><atom:updated>2023-01-14T00:00:00.000Z</atom:updated><category>writing</category><category>communication</category><category>feedback</category><category>collaboration</category><category>work-leadership</category></item><item><title>能力模型与自我评估：怎么知道自己在什么位置</title><link>https://liyuk.com/writing/2022/09/honest-self-assessment/</link><guid isPermaLink="true">https://liyuk.com/writing/2022/09/honest-self-assessment/</guid><description>能力模型最怕被当成迷雾。把&quot;我现在在哪、差距在哪、往哪走&quot;拆成可以自己测量的问题，而不是靠别人贴标签。</description><pubDate>Sun, 25 Sep 2022 00:00:00 GMT</pubDate><atom:updated>2022-09-25T00:00:00.000Z</atom:updated><category>writing</category><category>self-reflection</category><category>growth</category><category>feedback</category><category>work-leadership</category></item><item><title>筛选人和面试官到底在看什么</title><link>https://liyuk.com/writing/2022/07/campus-recruitment-training/</link><guid isPermaLink="true">https://liyuk.com/writing/2022/07/campus-recruitment-training/</guid><description>从简历、基础到项目阐述：面试不是猜标准答案，而是让人看见你的事实、判断、学习方式与合作方式。</description><pubDate>Fri, 01 Jul 2022 00:00:00 GMT</pubDate><atom:updated>2022-07-01T00:00:00.000Z</atom:updated><category>writing</category><category>career</category><category>campus-recruitment</category><category>engineering</category><category>work-leadership</category></item><item><title>结构化思维：把&quot;有条理&quot;聊成可以训练的事</title><link>https://liyuk.com/writing/2022/06/structured-thinking-at-work/</link><guid isPermaLink="true">https://liyuk.com/writing/2022/06/structured-thinking-at-work/</guid><description>结构化不是套模板，是让问题、证据、取舍和决定能被别人检查。一套可直接照用的训练与提问清单。</description><pubDate>Sat, 18 Jun 2022 00:00:00 GMT</pubDate><atom:updated>2022-06-18T00:00:00.000Z</atom:updated><category>writing</category><category>thinking</category><category>decision-making</category><category>communication</category><category>work-leadership</category></item><item><title>产品 sense：研发和产品怎么把&quot;这个功能值不值得做&quot;聊清楚</title><link>https://liyuk.com/writing/2022/03/product-judgment-for-engineers/</link><guid isPermaLink="true">https://liyuk.com/writing/2022/03/product-judgment-for-engineers/</guid><description>产品 sense 不是猜需求。从&quot;研发如何理解产品&quot;和&quot;产品到底在做什么&quot;两个角度，给出一份可照用的话题清单。</description><pubDate>Sat, 12 Mar 2022 00:00:00 GMT</pubDate><atom:updated>2022-03-12T00:00:00.000Z</atom:updated><category>writing</category><category>product-thinking</category><category>engineering</category><category>decision-making</category><category>product</category></item><item><title>工程师为什么需要产品判断</title><link>https://liyuk.com/writing/2022/02/engineer-product-judgment/</link><guid isPermaLink="true">https://liyuk.com/writing/2022/02/engineer-product-judgment/</guid><description>从完成需求到参与规划，工程师如何把技术实现放进用户问题与业务结果之间。</description><pubDate>Tue, 01 Feb 2022 00:00:00 GMT</pubDate><atom:updated>2022-02-01T00:00:00.000Z</atom:updated><category>writing</category><category>engineering</category><category>product-thinking</category><category>career-development</category><category>decision-making</category><category>work-leadership</category></item><item><title>一个人吃饭的低摩擦系统</title><link>https://liyuk.com/writing/2022/01/low-friction-solo-meals/</link><guid isPermaLink="true">https://liyuk.com/writing/2022/01/low-friction-solo-meals/</guid><description>不把做饭当成意志力考验：用少量固定选择，把采购、备餐、收拾和临时变动变成可持续的日常。</description><pubDate>Sun, 30 Jan 2022 00:00:00 GMT</pubDate><atom:updated>2022-01-30T00:00:00.000Z</atom:updated><category>writing</category><category>everyday-life</category><category>cooking</category><category>systems</category><category>field-notes</category></item><item><title>如何判断一段工作是否真的让你成长</title><link>https://liyuk.com/writing/2022/01/how-to-tell-if-work-helps-you-grow/</link><guid isPermaLink="true">https://liyuk.com/writing/2022/01/how-to-tell-if-work-helps-you-grow/</guid><description>不用职级、忙碌或短期评价来判断一段工作。看它是否让你的认知、时间和执行方式留下可带走的变化。</description><pubDate>Sat, 01 Jan 2022 00:00:00 GMT</pubDate><atom:updated>2022-01-01T00:00:00.000Z</atom:updated><category>writing</category><category>growth</category><category>career</category><category>reflection</category><category>work-leadership</category></item><item><title>团队成长不是扩张：效率、梯队与延续</title><link>https://liyuk.com/writing/2022/01/team-growth-is-not-expansion/</link><guid isPermaLink="true">https://liyuk.com/writing/2022/01/team-growth-is-not-expansion/</guid><description>团队不是人数与能力的简单相加。真正的成长，是在时间里形成更可靠的协作、可传递的经验，以及面对变化时仍能解决问题的能力。</description><pubDate>Sat, 01 Jan 2022 00:00:00 GMT</pubDate><atom:updated>2022-01-01T00:00:00.000Z</atom:updated><category>writing</category><category>team</category><category>leadership</category><category>growth</category><category>work-leadership</category></item><item><title>招聘与职业关系（一）：技术招聘，从“招到人”到建立长期判断</title><link>https://liyuk.com/writing/2022/01/technical-hiring-long-term-judgment/</link><guid isPermaLink="true">https://liyuk.com/writing/2022/01/technical-hiring-long-term-judgment/</guid><description>招聘不只是填补一个空缺，而是持续澄清团队需要什么、能提供什么，并在每一次选择中校准判断。</description><pubDate>Sat, 01 Jan 2022 00:00:00 GMT</pubDate><atom:updated>2022-01-01T00:00:00.000Z</atom:updated><category>writing</category><category>leadership</category><category>team</category><category>decision-making</category><category>communication</category><category>work-leadership</category></item><item><title>招聘与职业关系（三）：把“人脉”变成长期互惠关系</title><link>https://liyuk.com/writing/2021/11/relationships-as-long-term-reciprocity/</link><guid isPermaLink="true">https://liyuk.com/writing/2021/11/relationships-as-long-term-reciprocity/</guid><description>职业关系不是待开发的资源池，而是在真实协作、适度帮助与清楚边界中慢慢形成的信任网络。</description><pubDate>Mon, 15 Nov 2021 00:00:00 GMT</pubDate><atom:updated>2021-11-15T00:00:00.000Z</atom:updated><category>writing</category><category>relationships</category><category>communication</category><category>collaboration</category><category>career</category><category>work-leadership</category></item><item><title>Owner 意识与责任：把&quot;主动&quot;聊成边界清楚的事</title><link>https://liyuk.com/writing/2021/11/ownership-with-boundaries/</link><guid isPermaLink="true">https://liyuk.com/writing/2021/11/ownership-with-boundaries/</guid><description>责任不是无脑加班，也不是无脑接事。这套问题把&quot;谁决定、谁执行、何时升级、承担到哪里为止&quot;聊清楚。</description><pubDate>Fri, 05 Nov 2021 00:00:00 GMT</pubDate><atom:updated>2021-11-05T00:00:00.000Z</atom:updated><category>writing</category><category>ownership</category><category>leadership</category><category>collaboration</category><category>communication</category><category>work-leadership</category></item><item><title>成长里程碑：把&quot;我想成长&quot;聊成具体的样子</title><link>https://liyuk.com/writing/2021/08/specific-growth-milestones/</link><guid isPermaLink="true">https://liyuk.com/writing/2021/08/specific-growth-milestones/</guid><description>成长的话题最怕空。把&quot;我想成长得更快&quot;拆成情境、能力、证据与下一轮练习，让上下级都能照着问。</description><pubDate>Fri, 20 Aug 2021 00:00:00 GMT</pubDate><atom:updated>2021-08-20T00:00:00.000Z</atom:updated><category>writing</category><category>growth</category><category>self-reflection</category><category>feedback</category><category>work-leadership</category></item><item><title>时间管理：一场关于“忙”的对话</title><link>https://liyuk.com/writing/2021/06/one-on-one-time-and-commitment-boundaries/</link><guid isPermaLink="true">https://liyuk.com/writing/2021/06/one-on-one-time-and-commitment-boundaries/</guid><description>“最近很忙”是一句真实感受，但不是足够好的沟通。这套问题把忙拆成排期、容量、取舍与承诺，让上下级都能照着问。</description><pubDate>Thu, 10 Jun 2021 00:00:00 GMT</pubDate><atom:updated>2021-06-10T00:00:00.000Z</atom:updated><category>writing</category><category>communication</category><category>prioritization</category><category>collaboration</category><category>work-leadership</category></item><item><title>先用自己的产品：开发者如何建立真实反馈回路</title><link>https://liyuk.com/writing/2021/05/use-your-own-product-feedback-loop/</link><guid isPermaLink="true">https://liyuk.com/writing/2021/05/use-your-own-product-feedback-loop/</guid><description>自用不是&quot;多刷一会儿产品&quot;，而是一套从真实任务、有效证据到修复验证的反馈系统。</description><pubDate>Sat, 15 May 2021 00:00:00 GMT</pubDate><atom:updated>2021-05-15T00:00:00.000Z</atom:updated><category>writing</category><category>product-thinking</category><category>engineering</category><category>feedback</category><category>work-leadership</category></item><item><title>数据度量工作指南（五）：周期统计与复盘，让数字变成下一次行动</title><link>https://liyuk.com/writing/2021/05/periodic-metrics-and-retrospectives/</link><guid isPermaLink="true">https://liyuk.com/writing/2021/05/periodic-metrics-and-retrospectives/</guid><description>从日报、周报到问题复盘：如何维护基线、记录变化、判断影响，并把数据结论转成可验证的行动项。</description><pubDate>Sun, 02 May 2021 00:00:00 GMT</pubDate><atom:updated>2021-05-02T00:00:00.000Z</atom:updated><category>writing</category><category>data</category><category>metrics</category><category>retrospective</category><category>operations</category><category>technology</category></item><item><title>数据度量工作指南（四）：指标字典模板，把定义变成可复算的协作接口</title><link>https://liyuk.com/writing/2021/04/metric-dictionary-template/</link><guid isPermaLink="true">https://liyuk.com/writing/2021/04/metric-dictionary-template/</guid><description>一份可直接复制的指标字典模板，以及完成率、留存、转化、错误、体验质量和反馈指标的公开示例。</description><pubDate>Tue, 20 Apr 2021 00:00:00 GMT</pubDate><atom:updated>2021-04-20T00:00:00.000Z</atom:updated><category>writing</category><category>data</category><category>metrics</category><category>collaboration</category><category>measurement</category></item><item><title>数据度量工作指南（三）：指标分级，让数据先服务最重要的决策</title><link>https://liyuk.com/writing/2021/04/metric-tiers-prioritize-decisions/</link><guid isPermaLink="true">https://liyuk.com/writing/2021/04/metric-tiers-prioritize-decisions/</guid><description>不把指标平铺在看板上：用任务相关性、影响范围、行动性和数据可信度，为指标建立优先级，并在不同阶段选择该看什么。</description><pubDate>Thu, 08 Apr 2021 00:00:00 GMT</pubDate><atom:updated>2021-04-08T00:00:00.000Z</atom:updated><category>writing</category><category>data</category><category>metrics</category><category>collaboration</category><category>measurement</category></item><item><title>数据度量工作指南（二）：指标争论之前，先定义测量对象</title><link>https://liyuk.com/writing/2021/03/define-the-measurement-before-arguing-about-metrics/</link><guid isPermaLink="true">https://liyuk.com/writing/2021/03/define-the-measurement-before-arguing-about-metrics/</guid><description>一份可公开复用的指标词典：从请求、用户到任务，说明可用性、错误、延迟、性能和反馈数据该怎样定义、组合和解读。</description><pubDate>Sat, 27 Mar 2021 00:00:00 GMT</pubDate><atom:updated>2021-03-27T00:00:00.000Z</atom:updated><category>writing</category><category>data</category><category>metrics</category><category>measurement</category><category>observability</category><category>technology</category></item><item><title>数据度量工作指南（一）：数据口径是组织协作的接口</title><link>https://liyuk.com/writing/2021/03/data-definitions-are-collaboration-interfaces/</link><guid isPermaLink="true">https://liyuk.com/writing/2021/03/data-definitions-are-collaboration-interfaces/</guid><description>指标不是报表上的数字，而是团队用来描述同一件事的共同语言。先定义对象、事件、分母和时间，数据才可以参与决策。</description><pubDate>Mon, 15 Mar 2021 00:00:00 GMT</pubDate><atom:updated>2021-03-15T00:00:00.000Z</atom:updated><category>writing</category><category>data</category><category>metrics</category><category>collaboration</category><category>measurement</category><category>technology</category></item><item><title>从定义问题开始：一次一对一怎么开场</title><link>https://liyuk.com/writing/2021/03/shared-problem-definition/</link><guid isPermaLink="true">https://liyuk.com/writing/2021/03/shared-problem-definition/</guid><description>不知道怎么开场、不知道聊什么，就从&quot;把问题定义清楚&quot;开始。给上下级都能照着一问一答的问题清单。</description><pubDate>Mon, 15 Mar 2021 00:00:00 GMT</pubDate><atom:updated>2021-03-15T00:00:00.000Z</atom:updated><category>writing</category><category>communication</category><category>problem-framing</category><category>collaboration</category><category>work-leadership</category></item><item><title>主题式一对一：从&quot;不知道聊什么&quot;到一份话题地图</title><link>https://liyuk.com/writing/2021/02/one-on-one-from-definition-to-action/</link><guid isPermaLink="true">https://liyuk.com/writing/2021/02/one-on-one-from-definition-to-action/</guid><description>一次对话解决一个问题，每个主题 30 到 60 分钟。这套系列的使用方法、话题总览与收尾三原则。</description><pubDate>Wed, 10 Feb 2021 00:00:00 GMT</pubDate><atom:updated>2021-02-10T00:00:00.000Z</atom:updated><category>writing</category><category>communication</category><category>collaboration</category><category>self-reflection</category><category>work-leadership</category></item><item><title>成就感不是奖励：关于压力、交付与自我认可</title><link>https://liyuk.com/writing/2021/01/achievement-is-not-a-reward/</link><guid isPermaLink="true">https://liyuk.com/writing/2021/01/achievement-is-not-a-reward/</guid><description>成就感并不只来自结果或他人的赞美；它也来自完成承诺、认同职业、帮助他人，以及相信自己做的事有意义。</description><pubDate>Fri, 01 Jan 2021 00:00:00 GMT</pubDate><atom:updated>2021-01-01T00:00:00.000Z</atom:updated><category>writing</category><category>career</category><category>motivation</category><category>reflection</category><category>work-leadership</category></item><item><title>好的导师关系与新人 90 天计划</title><link>https://liyuk.com/writing/2020/10/mentor-relationship-and-first-90-days/</link><guid isPermaLink="true">https://liyuk.com/writing/2020/10/mentor-relationship-and-first-90-days/</guid><description>导师的价值不在替新人规划一切，而在共同建立目标、反馈与逐步放手的节奏；一份可执行的 90 天计划让这件事有迹可循。</description><pubDate>Thu, 01 Oct 2020 00:00:00 GMT</pubDate><atom:updated>2020-10-01T00:00:00.000Z</atom:updated><category>writing</category><category>mentorship</category><category>onboarding</category><category>career-development</category><category>feedback</category><category>leadership</category><category>work-leadership</category></item></channel></rss>