职业与工作方法blog.djmnet.org
从新手到大师，再回到新手
From novice to master, and back again (2013)
2014 — 2022，它一次次回到首页
黑点是上首页（≥ 50 分）的那次投稿，空心点是没冲上去的投稿，点越大分数越高。
导读
作者 David MacKenzie（GNU coreutils 中 ls、cp、mv 等工具的作者之一）讲述自己重新翻看多年前写的 su 工具源码时，发现自己已完全看不懂、需要从头学起的经历。文章探讨了从新手到专家、又回到新手的过程，以及遗忘与重新学习的普遍性。
为什么经久不衰：它触及每个技术工作者都会经历的体验——多年后面对自己写的东西恍如陌生人——提醒人们写文档、留注释最终是为了未来的自己。
HN 评论精选
连答案都是自己多年前写的，遗忘循环无处不在
过去十年里有两次我被某个问题彻底卡住，疯狂搜索之后终于找到答案……结果发现是 25 年前我自己在 Usenet 上写的。
dmd查看英文原文
Twice in the last decade I've been completely stuck on something, googled extensively, finally found the answer ... which I wrote, on Usenet, 25 years ago.
写文档本质上是写给未来的自己
这种事在我身上经常发生。别人因为某样东西是我写的而来找我，我却说：'让我先去读读手册'（因为一个月后我就记不清自己做了什么，所以总在查自己写的文档）。我总跟人说：'你以为我写这份手册是为了你？我可没那么无私，我是写给未来的自己的。'
nu11ptr查看英文原文
I can't even tell you how often this happens to me. People come to me because I wrote something and I then tell them: "Let me go read the manual" (because I can't remember what I did a month later, so I'm always consulting my own docs). I always tell people: "You think I wrote this manual for you, but I'm not that altruistic. I wrote it for future me." To be fair, not exactly the same thing. I typically remember I wrote it, just not what it does or how it works. :-)
不留说明的解决方案等于没解决
最沮丧的事莫过于遇到一个问题，却发现多年前有个已关闭的工单署着我的名字，却没写清我当时是怎么解决的。猜怎么着，现在的我只能从头再学一遍，因为当年的我太赶时间，懒得写下自己做了什么。
focusedone查看英文原文
Wow, epic! The most depressing thing is being presented with an issue and finding my name attached to a closed ticket from years before with no explanation of how I fixed it. Guess what, current me, you're going to learn this again from scratch because past me was in a hurry and couldn't be bothered to type out what he did. BSG - this has all happened before, and it will all happen again.
学得越深，越发现自己其实还是新手
我开始学物理时觉得自己一无所知，几十年后掌握了大部分内容。可当我试图理解最根本的问题——什么是时空？什么是希格斯场？质量究竟是什么？——我发现自己又回到了新手状态：我几乎什么都不知道。
BlakeCam查看英文原文
When I began studying physics I felt like a clueless novice. All those equations looked like chicken-scratch on paper. And, "What's the difference between kinetic and potential energy?" And there were so many concepts to understand - forces, masses, fields, charges, and particles. And differential equations seemed incomprehensible. Now, after a few decades I've mastered most all of that. Yet, when I try to grasp the real basics, like "What is space-time?", "How does superposition lead to a single macroscopic universe?", "What is the Higgs field?", "How did this universe 'start'?", "What exactly is mass?", then I realize I'm really back at novice again. I know almost nothing.
历次讨论
同类还值得读
用十年时间自学编程（1998）
Teach Yourself Programming in Ten Years (1998)
Peter Norvig 1998 年的经典文章，回应“21天/24小时学会编程”一类速成书，主张真正精通编程需要约十年持续、有意识的练习。
职业与工作方法上首页 11 次 · 2007–2025norvig.com编辑精选如何成为一名程序员：简短、全面而个人的总结
How to be a Programmer: A Short, Comprehensive, and Personal Summary
一篇广为流传的程序员成长指南，作者以个人经验系统总结了成为优秀程序员所需的各项技能——从调试、测试、沟通到团队协作与身心健康。
职业与工作方法上首页 6 次 · 2008–2015samizdat.mines.edu编辑精选不要自称程序员
Don't Call Yourself a Programmer
经典职业建议文章劝软件工程师不要把自己局限在“程序员”这个标签上，而要从公司业务角度说明自己创造的价值；文中讨论了成本中心与利润中心、头衔、求职与职业选择，也顺带批评了学术界的价…
职业与工作方法上首页 5 次 · 2011–2021kalzumeus.com编辑精选创作者的日程与经理的日程
Maker's Schedule, Manager's Schedule (2009)
Paul Graham 在这篇文章里把时间表分成两类：管理者的日程以小时为单位，会议可以填满一天；创作者（程序员、写作者等）的日程则以半天为单位，需要长时间不被打断的连续块。
职业与工作方法上首页 5 次 · 2009–2021paulgraham.com编辑精选为什么程序员的薪酬不与生产力成正比
Why programmers are not paid in proportion to their productivity
讨论为什么程序员的薪酬往往不随其生产力成比例增长：生产力难以客观量化，薪酬更多受组织预算、岗位定价和个人议价能力影响。
职业与工作方法上首页 5 次 · 2009–2022johndcook.com