写作与思考2019jvns.ca
让工作被看见：写一份“炫耀文档”
Get your work recognized: write a brag document
导读
Julia Evans 介绍「炫耀文档」(brag document)：定期记录自己做成了什么、帮了谁、学了什么，用来在绩效评估和升职谈话时有据可依。文章更重要的价值在于：它逼你跳出日常琐事，看见自己工作的主线与成长。几位读者在评论里补充了自己的实践方式——按人归档、截图存档、每日小记再汇总——对任何需要回顾和展示自己产出的人都适用。
可以直接用的写作要点
- 01
给自己建一份持续更新的「成果清单」，随手记下完成的任务、帮过的人和参加的会议，别等年底再凭记忆回想。
- 02
记录要分层：每天记细节，再定期汇总成「大局」，否则一年后连自己都看不出这些流水账的意义。
- 03
给成果留证：截图、录屏、动图存到内部 wiki，既能在演示翻车时救场，也方便别人复用你的工作。
- 04
这份文档不必给老板看，它首先服务于自我复盘——看清自己在做什么、在意什么、想改变什么。
HN 评论精选
助人的付出常不被看见，按人归档既便于复用代码，也能留下自己时间去向的证据。
我属于那种总想帮别人的人，可能是因为我不会说「不」，也可能是太自负不肯承认「我不知道」。我不写炫耀文档，但有一个叫 People 的文件夹，按我帮过的人分文件夹，再按他们来找我解决的问题分子文件夹。好处一是代码可以复用，二是能追踪时间花在哪了。我也试过写日记，但没坚持下来。我吃过亏才明白，乐于助人不一定被认可——有位经理甚至公开敌视这种做法，哪怕项目因此失败，这让我非常恼火。（这位经理读完 MBA 回来后推崇「爆裂鼓手」式管理，让我们去「摧毁」公司里的其他团队。）这也是我回到学界的原因之一，现在我的工作就是帮年轻工程师做到最好。
knolan查看英文原文
For whatever reasons, probably because I don’t say ‘no’ or I’m too arrogant to say ‘I don’t know’, I’m one of those people who always tries to help. I don’t keep a brag document but I do keep a folder called People where there are folders for the people I’ve helped and subfolders for each problem they’ve come to me with. On one hand it’s useful because I can recycle the code but it also helps track how I’ve spent my time. I also tried to keep a diary but this was less successful. I learned the hard way that being helpful is not always recognised, in fact I’ve had one manager openly hostile to the idea even if that meant the project would fail, it annoyed the hell out of me. (This manager came back from his MBA promoting a Whiplash approach to management and told us to actively ‘destroy’ the other teams in our company so there you go.) This was part of the reason I moved back to academia, now my job is to help young engineers be the best they can.
用截图和录屏代替实时演示，既避开环境问题，也让成果可被同事复用。
建议把截图也放进去！我上一份工作每月有一次非正式的桌前演示，向技术主管展示手头在做的东西。可要不是性命攸关，我连昨天干了什么都想不起来，于是这变成每月一次「翻版本库历史、先给自己总结、再讲给别人听」的例行公事。而且演示时机很难凑：本地代码刚改坏，或者动了个公共头文件要重编译一小时，就没法演示；为了演示一整天甚至好几天不敢乱改代码，又太浪费时间。往内部 wiki 上贴几张截图、动图或视频就解决了——就算你改坏了东西或正在编译，也照样能演示，还能顺手分享给想复用你工作、用你工具的同事，让他们一眼看到新功能藏在哪。
MaulingMonkey查看英文原文
Consider including screenshots! A previous job had "monthly" ad hoc desk demos to show off whatever we were working on to our tech lead. Since I can barely remember what I did yesterday if my life depended on it, this became a monthly "crawl p4 history and summarize for myself to summarize for others" routine. And of course, it's hard to demo when you've just broken your local checkout. Or touched a common header and need an hour to finish recompiling the entire codebase. And waiting around all day being conservative with my changes - or multiple days, in the event of delays or rescheduling - feels like wasted time. Slap some screenshots, gifs, or video on an internal wiki and bam - even if you can't demo in realtime because you broke something or are compiling, you can still demo. And now you can share it with coworkers who want to build upon your work, use your tools, etc. as a very easy way to see exactly where you've hidden the new feature in whatever bespoke thing you're doing!
炫耀文档的首要读者是自己：它能纠正「我什么都没做成」的错觉，提升信心。
「这篇博客不只是讲升职加薪。对我来说，这些想法更有用的地方在于帮我反思自己工作的主题、什么对我重要、我在学什么、我想在哪些方面做得不一样。」我刚给自己做了一份炫耀文档。虽然不确定会不会拿给经理看，但它确实让我的工作被我自己看见了。很多时候我觉得自己一天没干成什么，而这些感觉往往会盖过那些高效的日子。回看过去七个月，我震惊于自己居然做成了这么多事。我打算按月坚持下去，至少它让我的心理状态和信心好了一点。
WorkForPizza查看英文原文
"This blog post isn’t just about being promoted or getting raises though. The ideas here have actually been more useful to me to help me reflect on themes in my work, what’s important to me, what I’m learning, and what I’d like to be doing differently." I just went through and created a brag document for myself. While I'm not sure I'd show it to my manager, it certainly helped my work get recognized by me. There are a lot of days where I feel I haven't gotten a lot done, and those tend to overshadow the days I feel productive. Looking back on the past seven months, I was actually shocked to see how much I've accomplished. I'm going to try and keep up with this on a monthly basis, because at the very least it gave my mental health and confidence a little boost.
每日细记很有激励作用，但必须再做分层汇总，否则细节在长期毫无用处。
我以前就听过类似建议，所以今年春天换新工作时决定试一试。我每天随手记下做成了什么：关掉一个工单、帮人修了个 bug、开了个会，等等。很快我发现两件事。第一，这对我个人很有激励作用——不为别人，就为了下班时能有一份令人满意的清单。第二，这种颗粒度的记录，一年后无论是我还是我老板都用不上。你需要某种方式，把文章说的「大局」随时间聚合起来。我开始用一个应用按时间段分层汇总这些笔记，非常有用。可惜它还没到能分享的状态，也许有一天吧。
LifeIsBio查看英文原文
I had heard similar advice before, so when I started a new job this past spring, I decided to try it out for myself. As I go through the day, I write down what I’ve accomplished. I closed out a ticket, helped someone fix a bug, went to a meeting, etc. I pretty quickly noticed two things. First, I personally find this really motivating. For no one other than myself, I want to have a satisfying list at the end of the day. Second, neither I nor my boss are going to find this level of detail useful in a year. You need some way of aggregating (as the article mentions) “the big picture” over time. I’ve started using an app to help hierarchically aggregate these notes per time period, and it’s super useful. Unfortunately, it’s not in a shareable state yet, but maybe one day. :)
同类还值得读
不要想好再写，要写来思考
Don’t think to write, write to think
这篇短文主张不要把写作当成思考完成后的记录，而要把写作本身当作思考的工具：动笔的过程会逼出想不清楚的地方。
写作与思考2022 · 553 分 · 145 评4 条写作要点编辑精选写作即思考：学会自信地写作
Writing Is Thinking: Learning to Write with Confidence
这是一篇讲“写作即思考”的博客：作者认为写作不是把想好的东西誊写出来，而是借助写作本身把想法想清楚，因此写作者应当建立信心、敢于先写烂稿。
写作与思考2019 · 529 分 · 83 评4 条写作要点编辑精选如何用写作来思考
How to think in writing
这篇文章讨论的是「用写作来思考」：作者认为写作不只是把想清楚的东西表达出来，更是想清楚本身的工具——文字落在纸上，你才有机会看见自己思路里的跳跃、含混和漏洞。
写作与思考2024 · 424 分 · 120 评4 条写作要点编辑精选写作，帮你逃离默认的人生设置
Write to Escape Your Default Setting
文章的核心主张就写在标题里：写作是帮你逃离「默认设置」的手段——日常的思维和表达都有惯性默认的默认模式，而落笔能逼你跳出来，重新看清自己到底在想什么、要说什么。
写作与思考2025 · 407 分 · 93 评4 条写作要点编辑精选写作就是思考
Writing is thinking
文章以“写作即思考”为题，讨论写作不只是把已有想法记录下来，而是帮助澄清、组织和推进思考的过程。
写作与思考2025 · 330 分 · 128 评4 条写作要点编辑精选