Liyuk 关于技术、工作与日常的写作。https://liyuk.github.io/https://liyuk.github.io/writing/2012/01/network-bug/https://liyuk.github.io/writing/2012/01/network-bug/一篇写于大学早期的科幻短篇：当二维网路中的虫子得到三维知识，它失去的不是无知，而是行动的能力。Sun, 01 Jan 2012 00:00:00 GMThttps://liyuk.github.io/writing/2018/04/interview-questions-archive/https://liyuk.github.io/writing/2018/04/interview-questions-archive/2018 年春季求职后整理的面试与工程基础资料索引；保留它，提醒自己面试题从来不只是面试题。Mon, 02 Apr 2018 00:00:00 GMThttps://liyuk.github.io/writing/2018/07/frontend-first-ride/https://liyuk.github.io/writing/2018/07/frontend-first-ride/一份写给前端初学者的旧路标：信息获取、学习记录、算法练习、面试与实习，都只是开始。Wed, 04 Jul 2018 00:00:00 GMThttps://liyuk.github.io/writing/2018/04/product-apocalypse-one/https://liyuk.github.io/writing/2018/04/product-apocalypse-one/一个双十一购物场景的旧案例：在急着想方案之前，先分辨用户真正遇到的是什么问题。Thu, 05 Apr 2018 00:00:00 GMThttps://liyuk.github.io/writing/2020/01/why-technical-knowledge-bases-need-entry-pages/https://liyuk.github.io/writing/2020/01/why-technical-knowledge-bases-need-entry-pages/入口页不是链接堆栈，而是不断变化的项目留给团队的共同记忆：它帮助读者按任务进入、判断信息是否仍有效，并找到负责维护的人。Mon, 06 Jan 2020 00:00:00 GMThttps://liyuk.github.io/writing/2021/01/achievement-is-not-a-reward/https://liyuk.github.io/writing/2021/01/achievement-is-not-a-reward/成就感并不只来自结果或他人的赞美；它也来自完成承诺、认同职业、帮助他人，以及相信自己做的事有意义。Fri, 01 Jan 2021 00:00:00 GMThttps://liyuk.github.io/writing/2021/02/one-on-one-from-definition-to-action/https://liyuk.github.io/writing/2021/02/one-on-one-from-definition-to-action/一次对话解决一个问题，每个主题 30 到 60 分钟。这套系列的使用方法、话题总览与收尾三原则。Wed, 10 Feb 2021 00:00:00 GMThttps://liyuk.github.io/writing/2020/10/mentor-relationship-and-first-90-days/https://liyuk.github.io/writing/2020/10/mentor-relationship-and-first-90-days/导师的价值不在替新人规划一切，而在共同建立目标、反馈与逐步放手的节奏；一份可执行的 90 天计划让这件事有迹可循。Thu, 01 Oct 2020 00:00:00 GMThttps://liyuk.github.io/writing/2020/10/documents-are-collaboration-interfaces/https://liyuk.github.io/writing/2020/10/documents-are-collaboration-interfaces/一份技术文档的实用写法：先把结论和问题写清楚，再用合适的结构承接方案、进度与细节。Thu, 22 Oct 2020 00:00:00 GMThttps://liyuk.github.io/writing/2020/10/reusable-engineering-retrospective/https://liyuk.github.io/writing/2020/10/reusable-engineering-retrospective/工程复盘的价值不在于重述经过或追究个人，而在于把一次经历转化为能被验证、维护和复用的改进。Thu, 22 Oct 2020 00:00:00 GMThttps://liyuk.github.io/writing/2020/10/what-good-technical-sharing-should-change/https://liyuk.github.io/writing/2020/10/what-good-technical-sharing-should-change/把技术分享从定期演讲，变成选题、研究、讨论与沉淀相互连接的知识协作系统。Thu, 22 Oct 2020 00:00:00 GMThttps://liyuk.github.io/writing/2021/03/shared-problem-definition/https://liyuk.github.io/writing/2021/03/shared-problem-definition/不知道怎么开场、不知道聊什么，就从"把问题定义清楚"开始。给上下级都能照着一问一答的问题清单。Mon, 15 Mar 2021 00:00:00 GMThttps://liyuk.github.io/writing/2021/05/periodic-metrics-and-retrospectives/https://liyuk.github.io/writing/2021/05/periodic-metrics-and-retrospectives/从日报、周报到问题复盘：如何维护基线、记录变化、判断影响，并把数据结论转成可验证的行动项。Sun, 02 May 2021 00:00:00 GMThttps://liyuk.github.io/writing/2021/04/engineering-poc-faq-responsibility-boundaries/https://liyuk.github.io/writing/2021/04/engineering-poc-faq-responsibility-boundaries/面对跨职能需求，工程 POC 应如何分工、同步风险、处理变更与控制自己的负荷？这是一份面向真实协作场景的公开 FAQ。Wed, 21 Apr 2021 00:00:00 GMThttps://liyuk.github.io/writing/2021/04/metric-dictionary-template/https://liyuk.github.io/writing/2021/04/metric-dictionary-template/一份可直接复制的指标字典模板，以及完成率、留存、转化、错误、体验质量和反馈指标的公开示例。Tue, 20 Apr 2021 00:00:00 GMThttps://liyuk.github.io/writing/2021/04/metric-tiers-prioritize-decisions/https://liyuk.github.io/writing/2021/04/metric-tiers-prioritize-decisions/不把指标平铺在看板上：用任务相关性、影响范围、行动性和数据可信度，为指标建立优先级，并在不同阶段选择该看什么。Thu, 08 Apr 2021 00:00:00 GMThttps://liyuk.github.io/writing/2021/06/one-on-one-time-and-commitment-boundaries/https://liyuk.github.io/writing/2021/06/one-on-one-time-and-commitment-boundaries/“最近很忙”是一句真实感受，但不是足够好的沟通。这套问题把忙拆成排期、容量、取舍与承诺，让上下级都能照着问。Thu, 10 Jun 2021 00:00:00 GMThttps://liyuk.github.io/writing/2021/11/ownership-with-boundaries/https://liyuk.github.io/writing/2021/11/ownership-with-boundaries/责任不是无脑加班，也不是无脑接事。这套问题把"谁决定、谁执行、何时升级、承担到哪里为止"聊清楚。Fri, 05 Nov 2021 00:00:00 GMThttps://liyuk.github.io/writing/2021/08/specific-growth-milestones/https://liyuk.github.io/writing/2021/08/specific-growth-milestones/成长的话题最怕空。把"我想成长得更快"拆成情境、能力、证据与下一轮练习，让上下级都能照着问。Fri, 20 Aug 2021 00:00:00 GMThttps://liyuk.github.io/writing/2021/03/data-definitions-are-collaboration-interfaces/https://liyuk.github.io/writing/2021/03/data-definitions-are-collaboration-interfaces/指标不是报表上的数字，而是团队用来描述同一件事的共同语言。先定义对象、事件、分母和时间，数据才可以参与决策。Mon, 15 Mar 2021 00:00:00 GMThttps://liyuk.github.io/writing/2021/11/relationships-as-long-term-reciprocity/https://liyuk.github.io/writing/2021/11/relationships-as-long-term-reciprocity/职业关系不是待开发的资源池，而是在真实协作、适度帮助与清楚边界中慢慢形成的信任网络。Mon, 15 Nov 2021 00:00:00 GMThttps://liyuk.github.io/writing/2022/01/low-friction-solo-meals/https://liyuk.github.io/writing/2022/01/low-friction-solo-meals/不把做饭当成意志力考验：用少量固定选择，把采购、备餐、收拾和临时变动变成可持续的日常。Sun, 30 Jan 2022 00:00:00 GMThttps://liyuk.github.io/writing/2021/03/define-the-measurement-before-arguing-about-metrics/https://liyuk.github.io/writing/2021/03/define-the-measurement-before-arguing-about-metrics/一份可公开复用的指标词典：从请求、用户到任务，说明可用性、错误、延迟、性能和反馈数据该怎样定义、组合和解读。Sat, 27 Mar 2021 00:00:00 GMThttps://liyuk.github.io/writing/2021/05/use-your-own-product-feedback-loop/https://liyuk.github.io/writing/2021/05/use-your-own-product-feedback-loop/自用不是"多刷一会儿产品"，而是一套从真实任务、有效证据到修复验证的反馈系统。Sat, 15 May 2021 00:00:00 GMThttps://liyuk.github.io/writing/2022/01/team-growth-is-not-expansion/https://liyuk.github.io/writing/2022/01/team-growth-is-not-expansion/团队不是人数与能力的简单相加。真正的成长，是在时间里形成更可靠的协作、可传递的经验，以及面对变化时仍能解决问题的能力。Sat, 01 Jan 2022 00:00:00 GMThttps://liyuk.github.io/writing/2022/01/technical-hiring-long-term-judgment/https://liyuk.github.io/writing/2022/01/technical-hiring-long-term-judgment/招聘不只是填补一个空缺，而是持续澄清团队需要什么、能提供什么，并在每一次选择中校准判断。Sat, 01 Jan 2022 00:00:00 GMThttps://liyuk.github.io/writing/2022/03/product-judgment-for-engineers/https://liyuk.github.io/writing/2022/03/product-judgment-for-engineers/产品 sense 不是猜需求。从"研发如何理解产品"和"产品到底在做什么"两个角度，给出一份可照用的话题清单。Sat, 12 Mar 2022 00:00:00 GMThttps://liyuk.github.io/writing/2021/08/requirement-poc-responsibilities/https://liyuk.github.io/writing/2021/08/requirement-poc-responsibilities/工程 POC 不是项目秘书，也不是替所有人兜底；它的职责是让目标、承诺、风险和决策在跨职能协作中保持清楚。Tue, 17 Aug 2021 00:00:00 GMThttps://liyuk.github.io/writing/2021/09/product-overview-is-a-decision-model/https://liyuk.github.io/writing/2021/09/product-overview-is-a-decision-model/产品概览的职责不是收集尽可能多的事实，而是帮助读者在有限时间内建立共同问题、形成判断，并知道还缺什么证据。Wed, 15 Sep 2021 00:00:00 GMThttps://liyuk.github.io/writing/2023/01/clarify-feedback-and-commitment/https://liyuk.github.io/writing/2023/01/clarify-feedback-and-commitment/沟通的话题很大，但可以很具体。从"先澄清再反馈最后承诺"讲起，附一套工作沟通的完整问题清单。Sat, 14 Jan 2023 00:00:00 GMThttps://liyuk.github.io/writing/2022/09/honest-self-assessment/https://liyuk.github.io/writing/2022/09/honest-self-assessment/能力模型最怕被当成迷雾。把"我现在在哪、差距在哪、往哪走"拆成可以自己测量的问题，而不是靠别人贴标签。Sun, 25 Sep 2022 00:00:00 GMThttps://liyuk.github.io/writing/2023/02/evaluating-potential-with-care/https://liyuk.github.io/writing/2023/02/evaluating-potential-with-care/潜力不是履历或一次表现的标签。比起判断一个人“够不够聪明”，不如观察他怎样学习、行动、思考，以及从挫折中恢复。Wed, 15 Feb 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/02/indonesia-fourteen-days/https://liyuk.github.io/writing/2023/02/indonesia-fourteen-days/2023 年 2 月在雅加达的十四天：一座被折叠、被切开的城市，高楼和路边摊各自过着各自的日常。Mon, 20 Feb 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/04/communicating-organizational-change/https://liyuk.github.io/writing/2023/04/communicating-organizational-change/先同步已经官方确认的客观事实，不掩盖问题；再分别对上、对下和协作者说明目标、稳定性与新的协作方式。Tue, 04 Apr 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/04/escaping-the-resource-curse/https://liyuk.github.io/writing/2023/04/escaping-the-resource-curse/资源诅咒不是钱或人太多，而是资源让目标更细、结构更重、低质量决策更多，最终失去发现并解决高 ROI 问题的能力。Sun, 09 Apr 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/04/functional-teams-in-the-ai-era/https://liyuk.github.io/writing/2023/04/functional-teams-in-the-ai-era/职能线曾帮助专业能力高效运转；当工具降低工作流壁垒后，组织更应围绕全链路业务能力重新设计，而不是固守历史分工。Thu, 06 Apr 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/04/headcount-is-not-a-ratio/https://liyuk.github.io/writing/2023/04/headcount-is-not-a-ratio/人力配比只是动态概念。更重要的是在扩张、收缩和方案变化时，把目标、市场与资源约束及时对齐。Sun, 02 Apr 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/04/healthy-redundancy-and-harmful-overlap/https://liyuk.github.io/writing/2023/04/healthy-redundancy-and-harmful-overlap/容灾和复核是健康冗余；抢资源、抢项目和不清楚的授权导致的赛马，则会把组织推入零和疲惫。Mon, 10 Apr 2023 00:00:00 GMThttps://liyuk.github.io/writing/2022/01/how-to-tell-if-work-helps-you-grow/https://liyuk.github.io/writing/2022/01/how-to-tell-if-work-helps-you-grow/不用职级、忙碌或短期评价来判断一段工作。看它是否让你的认知、时间和执行方式留下可带走的变化。Sat, 01 Jan 2022 00:00:00 GMThttps://liyuk.github.io/writing/2022/02/engineer-product-judgment/https://liyuk.github.io/writing/2022/02/engineer-product-judgment/从完成需求到参与规划，工程师如何把技术实现放进用户问题与业务结果之间。Tue, 01 Feb 2022 00:00:00 GMThttps://liyuk.github.io/writing/2023/04/how-to-ask-yourself-better-questions/https://liyuk.github.io/writing/2023/04/how-to-ask-yourself-better-questions/好问题不是聪明的发问，而是把模糊的不适感转成可核验、可讨论、可行动的对象；这是一套用于工作、学习与复盘的日常练习。Wed, 12 Apr 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/03/defining-what-not-to-do/https://liyuk.github.io/writing/2023/03/defining-what-not-to-do/时间管理的核心不是塞满日历，而是根据角色、价值和机会成本明确承诺，也明确哪些事情此刻不做。Tue, 21 Mar 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/03/engineering-standards-without-bureaucracy/https://liyuk.github.io/writing/2023/03/engineering-standards-without-bureaucracy/好规范不是把每一步都变成审批，而是让最容易失真、返工和出事故的关键交接点变得可见、可讨论、可复用。Mon, 13 Mar 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/03/engineering-without-unique-value/https://liyuk.github.io/writing/2023/03/engineering-without-unique-value/技术不能凭空制造卖点，但工程师仍能帮助团队更准确地理解用户、缩短验证周期，并把隐含的约束变成可选择的问题。Sun, 05 Mar 2023 00:00:00 GMThttps://liyuk.github.io/writing/2022/07/campus-recruitment-training/https://liyuk.github.io/writing/2022/07/campus-recruitment-training/从简历、基础到项目阐述：面试不是猜标准答案，而是让人看见你的事实、判断、学习方式与合作方式。Fri, 01 Jul 2022 00:00:00 GMThttps://liyuk.github.io/writing/2022/06/structured-thinking-at-work/https://liyuk.github.io/writing/2022/06/structured-thinking-at-work/结构化不是套模板，是让问题、证据、取舍和决定能被别人检查。一套可直接照用的训练与提问清单。Sat, 18 Jun 2022 00:00:00 GMThttps://liyuk.github.io/writing/2023/03/frontline-engineering-management/https://liyuk.github.io/writing/2023/03/frontline-engineering-management/一线管理不是替团队多做一点事，而是持续产出更好的判断、可预期的交付，以及能自我修复的协作系统。Wed, 01 Mar 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/03/how-close-managers-should-stay-to-code/https://liyuk.github.io/writing/2023/03/how-close-managers-should-stay-to-code/管理者不必逐行审批代码，但若脱离一线细节，就无法判断风险、成本和团队真正的阻塞；关键是建立抽样理解，而不是微观控制。Thu, 09 Mar 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/03/information-sync-for-decisions/https://liyuk.github.io/writing/2023/03/information-sync-for-decisions/有效同步的目标不是把知道的一切都发出去，而是让特定读者在适当时间获得足以判断、协作或行动的信息。Mon, 27 Mar 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/03/one-on-ones-and-decision-rights/https://liyuk.github.io/writing/2023/03/one-on-ones-and-decision-rights/1-on-1 的核心是让上下级了解彼此目标与诉求；授权必须随着信息和角色边界发生，而不是把上下文误当作决策权转移。Fri, 31 Mar 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/03/product-engineering-trust/https://liyuk.github.io/writing/2023/03/product-engineering-trust/好合作建立在信任、信息互通和共同解决问题上；目标冲突时不要私自承诺，而要带着完整信息上升对齐。Wed, 15 Mar 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/03/reducing-context-loss-in-distributed-teams/https://liyuk.github.io/writing/2023/03/reducing-context-loss-in-distributed-teams/异地协作最贵的成本往往不是时差，而是上下文反复丢失。清楚的闭环责任、异步文档和有限的重叠时间能让协作更稳。Sat, 25 Mar 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/03/quality-is-shared-accountability/https://liyuk.github.io/writing/2023/03/quality-is-shared-accountability/每个角色对自己的交付负责，也共同对线上结果负责。质量闭环的关键是监控、快速止损、精确修复与复盘。Fri, 17 Mar 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/03/resolving-project-conflicts/https://liyuk.github.io/writing/2023/03/resolving-project-conflicts/多数项目冲突不是谁不配合，而是目标、事实或决策权没有被明确。先把这三件事说清，才能让分歧回到可解决的对象上。Sun, 19 Mar 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/03/shared-core-and-local-variation/https://liyuk.github.io/writing/2023/03/shared-core-and-local-variation/多地区系统既不能把所有差异硬塞进一个核心，也不能让每个地区重复建设。关键是识别稳定边界、保留扩展点，并明确模块所有权。Wed, 29 Mar 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/03/when-a-team-member-loses-motivation/https://liyuk.github.io/writing/2023/03/when-a-team-member-loses-motivation/动力不是靠口号或压力制造的。管理者能做的是分辨问题来自环境、角色、回报还是个人状态，并提供诚实而有限的支持。Sat, 11 Mar 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/03/why-code-decays/https://liyuk.github.io/writing/2023/03/why-code-decays/代码劣化并不主要来自某一次"写得差"，而来自局部变更不断绕过共同边界；真正要维护的是设计与协作的一致性。Tue, 07 Mar 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/03/working-under-resource-constraints/https://liyuk.github.io/writing/2023/03/working-under-resource-constraints/资源紧张不是一句"大家再努力一点"能解决的问题。团队需要把承诺、风险和投诉还原为事实，并公开作出取舍。Thu, 23 Mar 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/05/west-coast-daily-life/https://liyuk.github.io/writing/2023/05/west-coast-daily-life/2023 年 5 月的十五天：一边在另一个时区工作，一边开车、加油、停车、算账。最深的印象不是景点，是时差和"贵"。Mon, 15 May 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/04/anxiety-and-work-boundaries/https://liyuk.github.io/writing/2023/04/anxiety-and-work-boundaries/工作中的一对一不是心理咨询。把焦虑拆成"能控制的和不能控制的"，先聊认知，再聊具体压力与工作条件。Sat, 08 Apr 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/06/team-development-compounds/https://liyuk.github.io/writing/2023/06/team-development-compounds/团队培养的目的不是把经验灌输给每个人，而是让判断、协作与责任能够被练习、反馈和传递。Thu, 01 Jun 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/06/tokyo-wandering/https://liyuk.github.io/writing/2023/06/tokyo-wandering/2023 年 6 月六天：银座、涉谷、横滨、镰仓，以及密度、步行和"面积为什么要单独算钱"。Sun, 11 Jun 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/07/goals-retrospectives-and-next-actions/https://liyuk.github.io/writing/2023/07/goals-retrospectives-and-next-actions/规划和复盘不是为了完成任务。从制定目标的困难、到复盘的方法、再到以自我成长为导向，一套完整的话题清单。Sun, 16 Jul 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/08/career-growth-ten-questions/https://liyuk.github.io/writing/2023/08/career-growth-ten-questions/一份不压缩的问题库：围绕业务、技术、团队、个人判断与组织能力，逐项准备晋升材料、面试回答和阶段复盘。Tue, 01 Aug 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/03/mapping-an-unfamiliar-value-chain/https://liyuk.github.io/writing/2023/03/mapping-an-unfamiliar-value-chain/进入陌生业务或系统时，不要急着从局部方案开始。先画出使用者、流程、输入输出、关键约束和价值，才能知道该问什么。Fri, 03 Mar 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/11/my-reading-archives/https://liyuk.github.io/writing/2023/11/my-reading-archives/从 2021 到 2023 年的一份个人阅读记录：读什么、怎样记，以及一些还没有想明白的读后感。Tue, 14 Nov 2023 00:00:00 GMThttps://liyuk.github.io/writing/2024/01/insecurity-comparison-and-long-term-capability/https://liyuk.github.io/writing/2024/01/insecurity-comparison-and-long-term-capability/不安全感来自环境，也来自比较。先分清来源，再调整预期、拉长时间尺度，把注意力从"别人怎么样"拉回"我该练什么"。Sat, 20 Jan 2024 00:00:00 GMThttps://liyuk.github.io/writing/2023/12/anxiety-when-growth-slows/https://liyuk.github.io/writing/2023/12/anxiety-when-growth-slows/业务增速放缓时，团队会集体焦虑。先定"积极应对、分析问题、解决关键路径"的基调，再逐项聊清楚问题出在哪。Sun, 10 Dec 2023 00:00:00 GMThttps://liyuk.github.io/writing/2024/02/top-k-thinking/https://liyuk.github.io/writing/2024/02/top-k-thinking/面对一长串任务、问题和观点时，先定义判断口径，再找出真正排在前面的那几件事。Fri, 09 Feb 2024 00:00:00 GMThttps://liyuk.github.io/writing/2024/05/recruiting-brand-is-a-trust-system/https://liyuk.github.io/writing/2024/05/recruiting-brand-is-a-trust-system/招聘品牌不是美化职位，而是让合适的人相信：这件事值得做、团队有机会做成、自己能与同行者共同推动它成为现实。Mon, 20 May 2024 00:00:00 GMThttps://liyuk.github.io/writing/2025/03/referral-is-mutual-recognition/https://liyuk.github.io/writing/2025/03/referral-is-mutual-recognition/一次负责任的推荐，不是促成一次投递，而是帮助双方获得足够真实的信息，判断是否值得继续靠近。Sat, 01 Mar 2025 00:00:00 GMThttps://liyuk.github.io/writing/2023/06/from-zero-design-the-team/https://liyuk.github.io/writing/2023/06/from-zero-design-the-team/当既有梯队失效或需要重新开始时，先重建责任、标准和培养机制，而不只是重画一张分工图。Thu, 01 Jun 2023 00:00:00 GMThttps://liyuk.github.io/writing/2025/08/counting-practice/https://liyuk.github.io/writing/2025/08/counting-practice/从说清 1、2、3 开始，练习倾听、复述、回答与自我复盘，让混乱的信息获得可以行动的结构。Wed, 20 Aug 2025 00:00:00 GMThttps://liyuk.github.io/writing/2023/06/self-iteration-feedback-system/https://liyuk.github.io/writing/2023/06/self-iteration-feedback-system/所谓自我迭代，不是无止境地逼自己更快，而是看清目标、观察结果、调整行动，并在不确定中持续校准。Thu, 01 Jun 2023 00:00:00 GMThttps://liyuk.github.io/writing/2023/06/growth-paths-for-newcomers-core-and-leads/https://liyuk.github.io/writing/2023/06/growth-paths-for-newcomers-core-and-leads/成长路径不是职级清单，而是三种不断扩大的责任：完成任务、经营问题，以及让他人也能完成重要工作。Thu, 01 Jun 2023 00:00:00 GMThttps://liyuk.github.io/writing/2025/12/turn-spoken-ideas-into-decision-documents/https://liyuk.github.io/writing/2025/12/turn-spoken-ideas-into-decision-documents/把散乱想法蒸馏成一篇能讨论、能落地的文档：工具负责整理，人负责判断。Wed, 31 Dec 2025 00:00:00 GMThttps://liyuk.github.io/writing/2023/08/frontend-engineer-system-judgment/https://liyuk.github.io/writing/2023/08/frontend-engineer-system-judgment/职业发展不只是把更多需求做出来，而是逐步扩大问题定义、取舍和协作的责任范围。Tue, 01 Aug 2023 00:00:00 GMThttps://liyuk.github.io/writing/2026/05/departure-under-sunlit-flames/https://liyuk.github.io/writing/2026/05/departure-under-sunlit-flames/一段八年半职业旅途结束时的告别、回望与感谢。Fri, 29 May 2026 00:00:00 GMThttps://liyuk.github.io/writing/2025/04/from-skin-observation-to-product-selection/https://liyuk.github.io/writing/2025/04/from-skin-observation-to-product-selection/选彩妆不必先背色号或品牌：先在自然光下观察肤色、明度与当天的肤感，再把选择缩小到适合自己的颜色和质地。Sat, 12 Apr 2025 00:00:00 GMThttps://liyuk.github.io/writing/2025/02/gifting-question-framework/https://liyuk.github.io/writing/2025/02/gifting-question-framework/一份可直接使用的送礼操作指南：先确认人和场景，再从通用、定制、体验三类礼物里缩小选择。Thu, 20 Feb 2025 00:00:00 GMThttps://liyuk.github.io/writing/2025/04/everyday-full-makeup-decision-framework/https://liyuk.github.io/writing/2025/04/everyday-full-makeup-decision-framework/从妆前准备到妆容收尾，一套偏自然、注重持妆与骨相修饰的全妆实操顺序。Sat, 12 Apr 2025 00:00:00 GMThttps://liyuk.github.io/writing/2026/08/rebuilding-this-site/https://liyuk.github.io/writing/2026/08/rebuilding-this-site/这个站点正在从旧的静态博客，迁移为一个关于技术、工作与生活观察的个人出版物；也记录这次重建时做出的取舍。Fri, 14 Aug 2026 00:00:00 GMThttps://liyuk.github.io/writing/2025/11/technical-planning-business-and-competitive-analysis/https://liyuk.github.io/writing/2025/11/technical-planning-business-and-competitive-analysis/技术规划不是项目清单，本质上是两件事：理解要服务的业务（业务分析），理解与对手的差距和水位（竞品分析），再把它们连成目标、取舍与执行之间的因果链。Mon, 10 Nov 2025 00:00:00 GMThttps://liyuk.github.io/writing/2026/08/canvas-pitch-diligence/https://liyuk.github.io/writing/2026/08/canvas-pitch-diligence/记一个区分：商业模式画布是"做给自己看"，创业路演是"讲给别人听"，投资人尽调是"别人来查你"；三者的目的、重点和口径完全不同，别混着用。Sat, 15 Aug 2026 00:00:00 GMThttps://liyuk.github.io/writing/2026/08/management-retrospective/https://liyuk.github.io/writing/2026/08/management-retrospective/把过去几年在管理、协作与决策上反复出现的判断，收敛成一份只讲一次的总纲：判断、边界、对齐、上下文、闭环、资源、团队与复盘，每条各指向一篇展开。Sat, 15 Aug 2026 00:00:00 GMThttps://liyuk.github.io/writing/2026/08/vless-reality-return-proxy-notes/https://liyuk.github.io/writing/2026/08/vless-reality-return-proxy-notes/从 SSH 临时直连，到要照顾手机和家人的使用体验，最后用 sing-box 收敛为一套可维护的回国网络方案。Fri, 14 Aug 2026 00:00:00 GMThttps://liyuk.github.io/writing/2026/08/business-model-canvas/https://liyuk.github.io/writing/2026/08/business-model-canvas/企业投资课上学的商业模式画布，记给自己：九个格子各是什么、各自要回答的那个问题，以及"都满足才能做好项目"这句话为什么要按企业阶段来看。Sat, 15 Aug 2026 00:00:00 GMThttps://liyuk.github.io/writing/2026/08/structured-thinking-practice/https://liyuk.github.io/writing/2026/08/structured-thinking-practice/五镜法的实战篇：用面试、晋升、汇报、项目合作四个场景，演示怎么把结构化工具和五镜套到真实问题上。