资深工程师为何讲不清经验
推荐指数 35.0 NO. 011 · 2026.05.13
发布2026/05/12Score154Comments63
为什么值得看
文章指出资深开发者常因过度依赖抽象术语、缺乏具体案例而沟通失效。对技术管理者和需要晋升的工程师有直接参考价值，可借鉴其提出的"问题规避者"沟通框架。
编辑判断
HN 评论区的高赞反驳比原文更有价值：多数开发者认为"讲不清"的根源不是技巧问题，而是组织激励——公司奖励写代码而非教别人，晋升答辩从不考核知识传递。一位 Staff Engineer 提到他花了两年才意识到，所谓"沟通障碍"其实是自我保护：说得太清楚会被拉去 endless consulting，模糊表达才能保住 deep work 时间。
如果你正在带团队或准备升 Senior+，建议直接跳过这篇文章的方法论，先问自己两个问题：你的绩效考核里知识传递占多少权重？以及你上次因为"教会别人"得到明确奖励是什么时候？
社区反馈
意见分歧 62 条评论
核心争论：AI生成内容是否正在腐蚀技术写作质量，以及"问题规避者"框架是否过度简化资深工程师价值
I don't necessarily disagree with this conclusion, but the way it is written has a lot of AI prose smell that was extremely distracting for me.
I didn't get the AI vibe from it. At some point we are just going to have to get use to most stuff being written to some degree by AI. There will be different shades of usage and maybe we draw a line somewhere in there.
The written word is how people interact with LLMs. Clarity and precision in writing results in more effective prompting of LLMs. It is just as possible that leaning heavily AI writing will be seen as a marker of not being natively skilled enough at writing to prompt LLMs effectively because of the