职业与工作方法ams.org编辑精选
我希望曾被教过的功课（1996，Rota）
Lessons I Wish I Had Been Taught (1996) [pdf]
2020 — 2024，它一次次回到首页
黑点是上首页（≥ 50 分）的那次投稿，空心点是没冲上去的投稿，点越大分数越高。
导读
这是数学家 Gian-Carlo Rota 1996 年发表在《美国数学会会刊》上的经典短文，以十条建议的形式总结学术生涯中的经验教训，涵盖讲课技巧、写作、发表策略、费曼方法、如何面对错误与衰老等。文章虽面向数学家，但许多建议对更广泛的职业与创作同样适用。
为什么经久不衰：它把学术界的隐性智慧浓缩成简短可操作的建议，二十多年后仍被反复讨论，对任何做研究、写作或教学的人都有启发。
HN 评论精选
结合亲身经历印证费曼'常备十二个问题'方法的威力
费曼曾喜欢给出这样一条关于如何成为天才的建议：你要把十几个自己最喜欢的问题时刻放在心里，尽管它们大多处于休眠状态。每当你听到或读到新技巧、新成果时，就用你那十二个问题逐一检验，看它是否有帮助。我本周又实践了一次：重读三年前写的桌游设计日志，发现一个当初原型表现平平而被搁置的旧点子。我尝试改进它，想法不断演变，最终催生出一个在试玩中大获好评、并拿给出版商看的全新设计。
cableshaft查看英文原文
"Richard Feynman was fond of giving the following advice on how to be a genius. You have to keep a dozen of your favorite problems constantly present in your mind, although by and large they will lay in a dormant state. Every time you hear or read a new trick or a new result, test it against each of your twelve problems to see whether it helps.” Basically just did this again this week. I was re-reading a three year old board game design diary I had written, and came upon an old idea that I had put on the backburner after the prototype played just "ok". I tried to come up with ways to fix it for awhile, and the ideas I had then were so different they morphed into completely different designs (more specifically, it morphed into 1 different design, which bombed in playtesting, and then that morphed into a totally different design, which did really well in playtesting and I showed to publishers, and then reflecting on their feedback resulted in a completely new design sparking in my head). I thought about the problem for a few more seconds, and one new thing to try popped into my head, not a totally different game this time still keeping with the core mechanism, but a different method how players were given and used the cards, and I dug into it a bit more, and I decided on a different method of point distribution for the cards, and then thought a bit more, and the thought of adding abilities that encourage comboing based one previous or next cards played popped into my head, and then I decided to run with it, came up with a new prototype, tried it out, and it felt at least three times better, and felt more like a game that could be published. I have a game that is currently a finalist in a game design contest whose design had remained dormant for over a year because I was unsatisfied with it, but something made me think about it again and a new mechanism popped in my head and I tried that and felt a lot better about it. The Feynman method works for me, at least when it comes to designing board games. I don't mind shelving game designs for a long period of time anymore, since I have had so much luck with just thinking about them again every once in awhile and fresh new ideas popping into my head to improve the game, that likely wouldn't have happened if I kept forcing myself to think about that game.
列出文章十条要点，认为可迁移到职场
我很喜欢这篇文章。把文中的要点从学术界转译到企业环境需要一些功夫，我试着概括一下：讲课、黑板技巧、把同一成果发表多次、人们更可能因你的阐述性工作记住你、每个数学家只有几个招数、不要为错误担心、费曼方法、慷慨致谢、写信息量大的引言、为老年做好准备。
Forge36查看英文原文
(I really enjoyed this article) It does take some effort to translate from academia to a corporate environment I'll try do so in a reply. High level points: Lecturing Blackboard Technique Publish the Same Result Several Times You Are More Likely to Be Remembered by Your Expository Work Every Mathematician Has Only a Few Tricks Do Not Worry about Your Mistakes Use the Feynman Method Give Lavish Acknowledgments Write Informative Introductions Be Prepared for Old Age
补充相关资源：MathOverflow 上列举数学家招数的讨论
关于'每个数学家只有几个招数'这一点，MathOverflow 上有个相关问题试图列举所有这些招数，挺有意思的。
alderz查看英文原文
Related to the "Every Mathematician Has Only a Few Tricks" point, there is a Mathoverflow question https://mathoverflow.net/questions/363119/every-mathematician-has-only-a-few-tricks that tries to list all of those tricks, which is pretty interesting.
质疑重复发表建议在当今'publish or perish'环境下的副作用
我很好奇'把同一成果发表多次'的建议与'不发表就出局'的信条有何关联。我怀疑 1997 年是另一个时代。如今许多学者以超人节奏发表论文，与其说是从宇宙中提取了新知识，不如说是激进地重复发表已有成果，结果往往是极低的阅读和引用量。从外部看，很难在冗余中筛选出真正新的东西。科学出版的基础设施和格式或许可以从压缩、一致性和版本控制中受益。
mxschumacher查看英文原文
I wonder how the "Publish the Same Result Several Times" recommendation ties into the "publish or perish"-mantra. I suspect that 1997 was a different time. Many academics have a super-human publication cadence, not so much because of all the new knowledge they've extracted from the universe but because they aggressively re-publish their existing results. Very low read- and citation counts are common implications. From the outside, it seems hard to sift through all the redundancy. At the edge of knowledge it gets harder to verify what is genuinely new and what is a rehash. It feels like the infrastructure and format around scientific publishing could benefit from compression, consistency and version control.
历次讨论
同类还值得读
用十年时间自学编程（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