PHD的生涯

# 读博驱动力的五个阶段：过山车曲线

## 英文原文如下：

Transition Curve
The motivation during your PhD is not constant, and it resembles the phases that entrepreneurs experience and that Tim Ferriss describes in his post Harnessing Entrepreneurial Manic Depression: Making The Rollercoaster Work for You. Tim provides great advice for entrepreneurs, but this can easily be adapted to research and PhD life.

### Phase 1: Uninformed optimism

You start your PhD, everything is new and you find your project really cool. It feels like you are going to solve a big problem and you might get a big prize if you are ambitious and work well, maybe a patent, maybe a paper in a high impact journal. Sounds familiar? It is a similar feeling to starting in a new job, everybody is nicer than in the previous job and it is by far better organized. Well, give it some months, you’ll realize it is not that great.

### Phase 2: Informed Pessimism

You have been working for some time on your project, you understand the field better, but unfortunately you are still lost. You don’t see any good results in the near future and you start to realize that this project might be a bit too big for you. This phase is more severe if the content of your PhD is not a continuation from a previous work, if you switched fields.

### Phase 3: Crisis of Meaning

You are more or less in the middle of your PhD and you have a crisis like 40 year old guys have. Since you don’t have money to buy you a Porsche, you just cry in silence in a corner. You think “Is this all? Am I a failure?” The project is not as pinkful as you dreamt it, in fact, you are going to struggle and work your ass off to finish a minimally decent body of work. You feel that you have wasted a lot of time, that you did a lot of useless little projects. Now they seem useless, but you never know, maybe sometime later you connect the dots and they were the starting points of something great.

### Phase 4: Crash and Burn (optional)

While at Phase 3, if you don’t step aside fast from your negative feelings you are going to be screwed. Negativity might take over, leading you a mini depression. At this stage, many people think they have been wasting their time and they give up. They walk away with an unfinished PhD. Needless to say, we want to avoid this.

### Phase 5: Informed Optimism

Slowly you start to realize that your PhD thesis is not going to be as awesome as you thought. Whatever. At least you’ll get some publications, enough to graduate. Maybe the Nature paper has to wait for your post-doc. Who cares. You’d better finish a half-ass Phd than nothing. You are getting the grip of your field, you can contribute (something) to the state of the art. It should be enough. Good enough, you don’t need perfect.

This curve is fitted to PhD data collected during many years. This means everybody will experience a certain deviation from the values here predicted. Some phases will be mild while others can be extreme. At any stage, don’t be carried away by over-optimism/pessimism. Stay cool, be water my friend.

Interested in becoming a Scientist 2.0? Then visit my blog: http://juliopeironcely.com/

# “诺贝尔”为什么将中国神童拒之门外？（吴树新作）

——谢彦波

1978年，11岁的谢彦波挂着红领巾、带着一身传说、滚着一只铁环进入中科大。与“第一神童”宁铂齐名，他俩的故事“全国人民都知道”。

“谢彦波一直视安德森为神，去美国也是冲着安德森去的，但是一开始并没能排上安德森的博士生。一位台湾籍女教授收了他，老太太非常喜欢这个小娃娃，当儿子一样宠，谢彦波也非常适应，读得很好。没想到当他博士论文都基本写好了的时候，安德森的入学通知却来了！按道理，谢彦波本应跟着老太太读完博士再走，但他一心想在安德森门下出师，便迫不及待地离开了老太太，带着论文草稿投奔到安德森教授门下。

“刚开始，他在普林斯顿也读得非常好，据说还刷新了该校某个成绩总分的记录，并很快提交了论文。可偏偏就是那篇论文捅篓子了——安德森看看题目、翻翻前言，把文章一扔！

“物理是一门很悲哀的学科，尤其是谢彦波从事的理论物理研究，发展到一定程度就变得不可验证，比如说黑洞，谁见过黑洞？全都是几辈子科学家没法实证的，像玄学一样！正是因为没有检验标准，空想当道、学派林立、靠嘴皮子干仗就成了理论物理的现实情况。而谢彦波的论文，就踩了这个‘雷’。他引用的观点论据，不巧是跟安德森‘干仗’的对立学派，安德森怎么可能自扇耳光、让论文通过？他不好明说，便托辞‘你英文水平太差，我看不懂！

“谢彦波很愣，又非常崇拜安德森，还真的以为自己英文不过关，竟然花了两年时间在普林斯顿文学院读了个文学硕士，然后改好论文又送给安德森。安德森没辙了，只能委托旁人明确转告谢彦波：‘由于学派问题，你不可能靠这篇论文在我的门下拿到学位’。

“谢彦波没法相信这话，他眼里的安德森是多么伟大的科学家，又那么崇尚真理，怎么会有门户之见？你们都骗我！从那时候起，他就开始常常产生‘别人都在骗我’的幻觉。后来安德森拿他没办法，只好屈尊再让一步，托人转告谢彦波，可以介绍他在另外一个导师名下答辩。偏偏谢彦波到这一步还坚决不相信安德森会抛弃他，仍然执着地追随他死不回头。

“这一‘杠’足足9年，谢彦波与教授的矛盾几乎成为公开的秘密，就他自己感觉不到。在中科大一位副校长访问普林斯顿大学之前，恰巧又发生一起北大赴美留学生杀死教授的惨案，所以其他中国留学生建议到访的科大领导带谢彦波回国。副校长约谢彦波谈话过后，也感觉到有些担心，便直接带他随团回国。因为走得太急，谢彦波在普林斯顿大学宿舍里的所有物品都没来得及带走，都是后来同学帮忙打包邮回来的……”

5月，我来到中科大，预先“埋伏”在那位同学所说的教室里。看来这里是开放式教学，我旁边还坐着一位不修边幅的中年男人，上身套着一件脏得看不清本色的老式夹克衫，怀里抱着一只鼓鼓囊囊的红色环保袋，酷似街头拾荒者。见我落座，他挪了一下位置，似熟非熟地朝我笑笑。

# 在新加坡的这五年－－－第一年

2010年7月19日 星期一， 南京－新加坡，东方航空公司，MU771，09:50-16:00. 这是自己第一次买到新加坡的机票，也是自己的第一次出国。当时选择从南京出发，是因为自己在南京已经呆了整整五年。2005年9月2日从贵阳飞南京，在南京大学数学系读了四年，加上一年的休整。在南京的四年，得到了很多老师，同学和亲戚朋友的帮助，在南京的这几年应该是自己比较快乐的时光。在来新加坡之前，通过数学系的校友群，得知2003级的学长姜开封在07年已经过来，于是请求他帮忙在NUS附近找房子。当时的NUS不像现在，PGP宿舍是只提供给本科生住，是不给研究生住的，UTown宿舍也没有修好，Kent Ridge地铁站也没有修好。在种种不利的情况下，研究生就只能够在外面租房子住。当时多亏姜开封师兄的帮忙，在距离学校不远的地方找了一个屋子，离West Coast Plaza很近，Block 602，＃11-28。要是没有师兄的帮忙，估计当时真的只能够露宿街头了。说起来师兄也够给力，不仅帮我找到了住的地方，还专门跑到机场去接机，让人十分感动。这样也就罢了，连租房子交的押金都是师兄先垫着了，说以后发工资了你再还给我，因为刚来的PHD一般资金都比较紧张。以至于后来只要有南大的来新加坡，我如果知道的话，一般也会去机场接机，买张公交卡和电话卡，然后带到宿舍，简单的介绍一下NUS的生活情况，算是给后来人一点点微小的帮助吧。

2010年8月的第一周，是NUS传统的Orientation Week，新生都要参加，由各个学院的领导来介绍NUS的基本情况，然后研究生和博士生的一些基本要求之类的。当时自己的英语也不行，有的东西也听不懂，稀里糊涂的过了一周。碰巧那一周赶上新加坡的45周年，2010年8月9日，于是和同学去City Hall附近转了一圈，人山人海，当时的手机还是Nokia，定位系统都没有。新加坡这边的公交又不报站，Kent Ridge地铁站还没有修好，只能到Buona Vista或者Clementi转公交，因此出门之后就必须要记住路。当时8月9日在外面瞎跑了一天，晚餐吃的也是快餐，总算体验了一下新加坡热闹的国庆。

2011年是自己第一次不在国内过年，不过这边也没啥过年的气氛，都是自己过自己的，无非就是PHD自己做点饭来吃吃。而且过年也只有两天的假期，何况系里面不让PHD在这段时间用自己的假日回家过年，理由是有助教的任务。于是没办法，只能够在新加坡过年。过年的时候，几乎所有的店铺都关门，超市也关门，只能够自己提前买好吃的，储备好自己的食物，免得没饭吃。这个学期和上一个学期有很大不同，上个学期几乎不出门玩，几乎都在学校度过，但是这个学期在新加坡反而去了不少的地方。动物园，植物园，中华园，圣淘沙等，该吃的东西也吃了不少，回去之后总算可以给亲戚朋友说一下新加坡的一些基本情况。

# NUS 数学系 PHD 论文提交-2015年

2015年，终于在新加坡国立大学（National University of Singapore）数学系把博士论文交上了，于是写一个大致的流程供大家参考。

# 科研这条路

### 3. PHD生涯。

NUS的第一个学期就收到一篇90页的论文，不过论文里面有个巨大的漏洞，希望自己能够找出来并且把它补上。第一个学期选择了太多的课程，分析，代数，拓扑，PDE，导致自己也没啥时间弄这篇论文。第一个学期的唯一收获就是把博士生资格考试顺利通过了。到了第二个学期，开始读论文了，虽然自己之前也读过论文和相应的书籍，但是给PHD的课题怎么可能那么容易就完成。如果那个漏洞那么容易就补上了，怎么可能十几年没人做那个问题。查一下网上的资料，2006年有人做出了类似的一个问题，不仅顺利发了Annals of Mathematics，还给了国际数学家大会45分钟的报告。相比之下，可想而知自己的这个博士课题有多难。在这个时候自己也没多想，也没想过换一个容易一点的问题，总想着自己一定能够做出来，然后当时办公室位置紧张，没分到办公室座位，于是自己天天都去图书馆呆着，就带着自己的这篇论文，在图书馆里面一页一页的看。

$f(z)=z^{\ell}+c$

### 4. 经验总结。

(i) 极强的心理素质：之前高中，本科遇到的练习题，努力一下，和同学讨论一下，说不定都能够搞出来，花上几个小时，几天，甚至几周，基本上就能够搞定。但是对于一个博士生来说，没有任何课题是在几天，几周，甚至几个月之内就能够搞定的。以前在高中和本科的时候都能够不停地做出数学难题，于是就能够给人带来快感，让人越来越有动力，越来越想研究数学。但是在读博士的过程中，这种感觉肯定会烟消云散。取而代之的是长期做不出来问题，读论文带来的痛苦，思考问题带来的绝望。无论一个学生的本科成绩多么的优秀，在有科研经验的老师面前，真的是不算什么。被老板bs很正常，科研成功一次就可以毕业了，甚至就能够功成名就了（参见张益唐）。在这个非常漫长的四年，五年，甚至六七年的岁月里，一个学生要是没有这点心理素质就不要混下去了。正如图片所示：读博士之前一直以为读博士努力下去就会一帆风顺，按时到达。结果实际的情况确是第二种，道路崎岖不平，各种意想不到的艰难困苦，只有克服了这些困难，才能够在PHD这条路上走下去。

(ii) 从开始PHD的那一刻开始，就必须忘记之前自己取得的所有成绩，一切从零开始。以前很轻松的写一下本科毕业论文就可以获得优秀，能够讲讨论班，甚至足够在所谓的SCI杂志上发表，这些只能够说明在本科生当中属于佼佼者。但是开始读博士之后，这些就变得不算什么了。好比你一开始住在五层小楼里面，身边都是平房，自然显得很强。但是后来随着自己的成长，坐标系也就悄悄的发生了变化，身边的人也跟着变化，对手已经不是本科生，而是从本科生中间选出来的优秀者，难度显而易见的增加了许多。

(iii) 对于一个普通的博士生来说，自己想独立搞科研几乎是不可能的，想脱离老板而独立搞科研完全是自寻死路。一开始读博士的时候由于本科的习惯，总自以为自己的想法很牛逼，很可能做出大东西，后来发现这是根本不可能的。作为老板，在科研领域已经打拼了十几年，在经验和能力上面通常都在博士生之上。通常一个博士生自己提出一个东西，要么是别人做过了，要么是根本没有什么意思，没有人在乎。如果让博士生自己选择论文课题，要么选择得太难，根本不可能完成，要么就是别人已经做过了，根本没有继续研究的必要。对普通的博士生来说，奉劝大家，基础不够就老老实实从底层做起，从老板推荐的论文和书籍一点一点的慢慢开始，千万不要想自己去选择一些论文课题来做。往往一个领域有着自己非常难的问题，通常这些问题是不能够直接留给博士生来做的。这个时候不能够从正面去攻取这些题目，需要有一定程度的迂回，而这些迂回往往依赖于导师在本领域摸爬滚打多年的经验。此时导师给学生推荐的书和论文会从侧面帮助学生理解问题，研究问题甚至解决问题提供非常大的帮助。在这个过程中，导师很可能根据学生的科研进度提出阶段性的题目，以降低学生科研的难度。通常来讲，老板提出的问题和想法，博士生有的时候哪怕只是取得了部分的结果和进展，都会远远高过自己独立选择的题目。

(iv) 在博士的生涯中，曾经见过有的老板会帮助学生写论文，甚至送论文给学生，但是并不是所有的老板都会做这些事情。博士生自己做不出来问题，很多老板通常是不会给予非常直接的帮助的，这个时候就需要博士生自己想办法来解决问题，克服障碍。在学校里面，通常的观点是：写不出论文是学生的问题，不是老板的问题。对于一个数学系的博士生来说，即使你的论文想法已经非常成熟，细节全部都能够过去，要把它写成一篇能够发表的论文也是一条非常艰难的路，而且这条路也很不好走。之前本科的时候，一般的关注点都是学生学了多少东西，懂得多少东西。到了博士阶段，已经没有人在乎学过多少东西，在乎的是做出了什么结果，能够发表什么样的文章。要发好的杂志，就需要一个好题目，这个问题通常都是难题。在这些问题前面，每个人都是平等的，都是一个一个独立的灵魂在奋斗。此时此刻就需要博士生自己克服很大的心理障碍，想毕业就要一直坚持做自己的课题，坚持下去才能够知道自己能不能够成功，才能够知道自己究竟能够走多远。在这个过程中，根本不敢去想能够走到哪一步，只能够咬紧牙关坚持走下去。科研这种只有一个人在走的路十分考验一个人的忍耐力和承受力。跟别的事情不一样，比方考试什么的，都是大家一起混，怎么混一般都不至于混到最后。但是科研这种事情，就和一个人到海里面游泳一样。游着游着，猛一回头，尼玛就只有自己一个人在游泳，而且已经看不到岸了，只能够一个人努力往前游。做科研难题的时候，只有自己能够帮助自己，只能够一个人竭尽全力地往前走。

(v) 对于数学系的人来说，由于不需要像别的专业一样做实验，所以时间非常自由，除了干一些教学工作，剩下的时间都是自由安排。这种自由职业者如果时间安排不当，很容易产生拖延症，陷入PHD的时间陷阱而不能自拔。对于搞纯数学的PHD来说，一个PHD的课题绝对不是在几个月之内就可以完成的，一定会有一段时间没有任何的进展和突破。这个时候由于要克服自己的心理压力，很容易在自己的科研课题上面产生拖延症，好比牛顿第一定理，在没有外力的催动下，自己的课题一定会停滞不前，能毕业日期也就离自己越来越遥远。如果出现这种问题，需要及时克服自己的心理障碍，战胜拖延，免得造成更大的困扰。

# ［转载］关于如何写正式英文email的总结

1．要用教育网邮箱，避免被过滤掉。地址格式直接用wi@cqu.edu.cn>避免其他格式某些系统不支持。

2．地址栏只有一个地址，不要同时发给几个人，尤其是不要让一个接收者知道。就是避免在接收者收到的邮件里面看到正文前面一串邮箱地址：（1）不安全，把某些人的邮箱传给了不认识的人。（有时候居然发现有些人写满自己个人信息群发邮件。。）（2）一个问题发给两个人，两个人如果都觉得对方会回答，你的问题就没人回答了。

3．写完，发之前要通读几遍，找错误，最好找别人读一下，看会不会被误解。尤其是要核对后面“句型和句子的注意事项”中的问题，确保在邮件中你显得比较专业，比较认真。。尤其是在找人帮忙或问问题的时候。

4．如果问问题或索要资料，要交代清楚背景，避免收件人不知所问。

1 . 称呼和正文之间，段落之间，正文和信尾客套话之间一般空一行，开头无须空格。有多个要点时,分项列举或分行以便于阅读。（参考最后的例子）；

2. 介绍自己。

3. 不要把某个词全部大写，这样常会被认为是在吼叫或骂人（很不礼貌）。如果要强调某些词语或句子用底线,斜字,粗体就可以了. 如：MUST change to OS immediately. 外国人就觉得不礼貌和喝令人一样. 要强调的话。

4. 不要用简写和笑脸等符号 J，不要用长词和不常用的词语。简单的单词便于理解。

（ 其实估计我们也只会常用的词语）。。。

5. 整个email不要太长，每个段落不要太长，每个句子不要太长，不要用结构复杂的句子。

1. 要写一个 meaningful 标题。不要太宽泛，不要含糊不清,不要太长，一般不要超过35个字母，只需要将位于句首的单词和专有名词的首字母大写.

“Product A information “ is good than “product information”.

“News about the meeting” vs “Tomorrow’s meeting canceled”.

professional trainees from sister company should abide by rule of local company（太长）

“Could I please get the assignment for next Wednesday?”

Dear Professor Sneedlewood  即：Dear Professor +lastname, 千万不要用first name称呼。千万不要写错名字,头衔（会很让人反感），有的人有荣誉学位就不喜欢用一般头衔.

Dear Committee Member:  注意:冒号是可以用的.

1. 段落开头写重要的和要强调的事情.同样重要的事情要写在句子首.

（1）Because he was unable to attend the meeting personally, he forwarded his congratulations on cassette tape.
（2）He forwarded his congratulations on cassette tape because he was unable to attend the meeting personally. 两者强调的事情就有分别了.

2. 轻重有分， 同等重要的用and来连接，较轻放在次要的句子里.

1. 用主动句型而不是被动。

“We will process your order today” is more personal than “your order will be processed today”. 后者用太多，sounds unnecessarily formal.

2. 那么I和you呢?好烦好烦.一般来说,收信人的利益比较重要,名义上都要这样想.给人尊重的语气就一般不会错了. 多用you有时会有隔阂的感觉.
You will be pleased to learn that you have been selected to serve on our advisory board. Your prompt response will be appreciated. (好像欠你一样)
I am pleased that our board has selected you as the best qualified candidate to serve on our advisory board. I hope you’ll agree to serve. (这就友善多了)
Your book was well written and comprehensive. (不用你来判断我呀~~)
I thoroughly enjoyed your book and found an answer to every one of my questions about performance appraisals. (客气一点,人家受落)

3. 亲切,口语化是比较受欢迎! 用宾词和主动的词,让人家受落.

（2） We sincerely appreciate your information. 明显地,我们会喜欢第2句.

“Could you please email me the page numbers for the next reading? Thanks!” sits better than “I need the assignment. Please send it.” It’s a Golden Rule kind of thing, right?

5. 不可主客不分或模糊.

Deciding to rescind the earlier estimate, our report was updated to include $40,000 for new equipment.” 应改为：Deciding to rescind our earlier estimate, we have updated our report to include$40,000 for new equipment. (We决定呀, 不是report.)

6. 结构对称,令人容易理解. The owner questioned the occupant’s lease intentions and the fact that the contract had been altered with ink markings.

7. 单数复数问题:

8. 动词主词要呼应. 想想这两个分别:
1）This is one of the public-relations functions that is underbudgeted.
2）This is one of the public-relations functions, which are underbudgeted.

9. 时态和语气不要转变太多.看商务英语已经是苦事,不要浪费人家的精力啊.

10. 标点要准确.

11. 选词正确. 好像affect和effect, operative和operational等等就要弄清楚才好用啦.

12. 拼字正确. 有电脑拼字检查功能后,就更加不能偷懒.

13. 意思转接词要留神. 例如: but (相反), therefore (结论), also (增添), for example (阐明). 分不清furthermore和moreover就不要用啦.

14. 修饰词的位置要小心,

15. 用语要肯定准确.切忌含糊.

16. 立场观点一致. 少用被动语.

17. 求人做事，最后写:thanks 即可.

1. 格式问题，

Ken Green

Vice president, Unicom China.

Ken Green

Vice President of Unicom China （其实就多个”of”,但没办法要专业…要专业.）

2. 书信的结尾致意要留意,弄清大家的关系才选择用词,例子:
（1） Very Formal非常正规的(例如给政府官员的)
Respectfully yours, Yours respectfully,
（2） Formal正规的(例如客户公司之间啦)
Very truly yours, Yours very truly, Yours truly,
（3） Less Formal不太正规的(例如客户)
Sincerely yours, Yours sincerely, Sincerely, Cordially yours, Yours cordially, Cordially,
（4）Informal非正规的(例如朋友,同事之类)
Regards, Warm regards, With kindest regards, With my best regards, My best, Give my best to Mary, Fondly, Thanks, See you next week!

To: Carmine Prioli <prioli@social.chass.ncsu.edu>

Subject: Will be absent next Wednesday. Could I get the assignment?

_______________________________________________________________

Hi, Dr. Prioli-

I will be playing my cello for a friend’s conference performance in San Antonio, TX next Wednesday, Thursday, and Friday (November 16, 17, & 18).

I am afraid my Wednesday flight leaves before your Colonial Literature class. Could I please get the assignments for that day so I can prepare for Monday?

Thanks!

Susanna Branyon
Colonial Lit, MW 1-3pm

How to write clear emails to your professor (or, why I currently think my undergrad students are rockstars)

we talk about how to address faculty and staff (a hint: call them “Dr” or “Professor” as a default, and they may tell you to call them something else if you’re lucky).

Together we came up with the following guidelines:

Write a clear subject line that actually summarizes what the question is and what it might be connected to in the course.

Address me in the email, and remember to call me “Dr.” or “Prof.”

Give me some context for the question, situating it in the particular assignment or activity you’re working on.

Punctuate. Capitalize appropriately. Use complete words and sentences; this is not texting. Check your spelling.

Be specific and detailed about what the difficulty or challenge is regarding.

Ask an actual question, rather than leaving it up to me to infer what you don’t understand.

Be nice and thank me for answering.

Sign your full name and give what ever institutional markings might be helpful for me to keep this in context.

Dear Dr. Pawley,
Our lab group was working on the class project for ENGR 126 and we didn’t understand one of the requirements (#4). Can you please clarify for us what you mean by “what the experts say”?
Thanks
Astu Dent, Team 4

Sounds simple but so many people screw it up. Seth talks about writing a personal email. But I see these mistakes in the emails I get from job seekers and people trying to get my attention for some other professional reason. Listen up staffing tools vendors, agency recruiters and the people that want me to introduce them to some nameless person within Microsoft that they can contact about their business idea/product concept, etc. Yeah, let me get right on that. I have a ton of extra time and absolutely no priorities. And I definitely would not rather be spending my time doing something else. Ooh, snarky.

I think the worst offenders are the folks that contact me through LinkedIn looking for a job. I can’t even tell you how many of these rules have been broken. But let’s just say that cut and paste isn’t always your friend. If you don’t take the time to craft an email that, say, addresses me by name and/or references my company, then can you really expect that I will take the time to review your resume and forward it along to the recruiters here? Really?

I get a lot of mail from people that don’t really know what they want to do at Microsoft. Oh yes, I actually do. If they don’t know, how the hell am I supposed to know? I always send them to our career site to find some positions that they could be interested in. I would like to believe that they are just experiencing a momentary lapse of reason and are not expecting me to wade through all of our open positions in order to find the ones that would be a fit for their background and that they would personally enjoy. You know, because I know them personally.

The thing is that I actually want to help people. But not if it’s a waste of my time. And helping people that don’t have the good sense to not spam a bunch of staffing folks or do a little research so they know who they are asking for help is definitely wasting time. So here are some of my rules for sending a job search email:

1) Address me personally. If you don’t, I know….KNOW that you are cutting and pasting. And if that is the case, I know that you think that your job search is a numbers game. Knock on enough doors, etc. That makes me think that you are not a sought after prospect. Or, it makes me think you are lazy. Either way… not good.

2) When and if you do address me by name, make sure it’s my name. We all know what mail merge is. Refer to #1 above. And on the same note, that whole “Sir/Madam” thing? Come on! Even if you are not from the US, you have access to the same interwebs I do and can identify “Heather” as a female name. Nobody has ever called me “madam” to my face…ever! Or “sir” for that matter.

3) You don’t have to send me a long email with a narrative of your professional life. It’s best to tell me where you work and what you do plus a little about any previous work that is relevant to the position that you are looking for (“I am currently working as an account manager at XYZ and previously worked at ABC in tech support.”), plus any experience with specific markets (“My experience is primarily in the healthcare and biomedical industries.”) and what you are looking to do (“I would like to get back into a role where I can utilize both my account management and technical expertise. I noticed a position open at Microsoft for a Technical Account Manager, focused in healthcare and feel I would be a good fit.”). The goal is to get the recruiters to view your resume, not to restate the resume. The email is, at most, a teaser.

4) If you are open to relocation, state it up front. It’s one of the first questions we will ask you.

5) If you reference specific positions or groups, include a job code from our career site. You should spend time on our career site looking regardless. Including job codes helps me get your resume to the right person. It also shows me that you are serious.

6) Don’t tell me you are willing to “do anything.” Wow, that is a red flag! OK, well first, nobody is qualified to do any/every job. So it’s not smart. And it sounds desperate. I know that it’s hard if you are out of work; that is probably an understatement. But despite this fact, you want to make employers feel that they would be fortunate to get you. Because you got skillz.

7) Don’t tell me about your personal life. There is some stuff that I am more comfortable not knowing. If you are sending an email to inquire about open positions, include only information that is relevant to the position. I know that people ask for advice and include a little personal info, and that is fine. But if you are reaching out to me about a position, I don’t need to know that the reason you want to relocate is that your mother-in-law is living with you and you’d like to leave her behind because she chews loudly. Just sayin’.

8) Attach your resume from the beginning. I’ll look at it and forward it along to any appropriate recruiters. It’s how I roll. So withholding it and asking me to tell you more about the position is just going to result in extra emails.

9) You can ask me to spend some time talking to you about a position or group, but it’s not going to happen. Of course we all want that. It might be reasonable if you are reaching out to a recruiter and you have all of the requirements of an open position (be honest with yourself about that too), but consider whether the person you are reaching out to is the recruiter for the open positions or even a recruiter at all. And to that end…

10) When you are reaching out to someone at a company, especially when you are asking for something, take a little time to research them. Just search on their name (might I recommend that you Bing them?).  It might inform how you engage that person. For example, if someone did a search on my name, they would find that I am not currently a recruiter but I do work in Staffing, that I am female (picture frequently accompanying my contact info), that I am a blogger, that I am open to forwarding resumes and that I provided a list of how to write an effective job inquiry email.

I don’t mean to be overly critical. Any one of these things is not a deal-breaker but most of it seems like common sense. You obviously want to make a good impression and get your resume in the right place ASAP. So yeah, consider this a little email tough love.

http://www.cqumzh.cn/uchome/space.php?uid=102519&do=blog&id=278386

# ［转载］写英文 Email 要特别留心这些点，一些原则私信也适用

Email 要以收信人为主题

Email 要简洁明了

Email 要避免套话空话

• at your earliest convenience （直接说 when you can 或者 soon）
• please find enclosed 或者 I have forwarded （直接说 I have sent you）
• please do not hesitate （不需要说，直接删掉）
• 过于书面的表达。比如 herewith、aforementioned、hereby、herein 这样的词语，或者非常老派的表达方式，让人感觉你是从一本出版于 60 年代的语法书上抄来的。
• 过于口语化的表达。这个对于非英语母语的人来说，写出过于口语化的英语来其实是不太可能的。比如说，用 Let’s touch bases next week 代替 Let‘s talk next week，用 bottom line、team player、square one 等等类似的口语化词汇， 这些都属于所谓的 slang 或者 buzzword。这样的表达会让人觉得你不太职业，给人不信任的感觉。其实，现在的中文里有大量这样的例子，“碉堡”“么么嗒”“蛮拼的”之类的最好不要用在除了非常私人的信件以外的任何 Email 里。

Email 要注意性别指代

• 不要说 Each employee must show his identification，请用 Employees must show their identification.
• 不要说 By the age of three, a child should be able to feed and dress himself，请用 By the age of three, a child should be able to eat and get dressed without help.
• 不要说 Although a nurse often comes to the job without computer experience, she can easily be trained to use the hospital software，请用 Although a nurse often comes to the job without computer experience, this person can easily be trained to use the hospital software.
• 不要说 actress，请用 actor。（可以注意好莱坞的采访或者发言，大多数女演员会说 as an actor… 医生都是 doctor，没有 doctress，所以演员都是 actor，越来越少的人用 actress 这个词）
• 不要说 fireman，请用 firefighter。
• 不要说 maid，请用 housekeeper。
• 不要说 policeman，请用 police officer。
• 不要说 mailman，请用 mail carrier。
• 不要说 salesman，请用 sales representative 或者 sales agent。
• 不要说 waiter 或者 waitress，请用 server。
• 不要说 mankind，请用 humankind。

Email 的格式和字体

Email 的段落应该尽量短小，尽量避免一整段的长篇大论，尤其是第一段更应该紧抓重点。段落首行不需要缩进，单倍行距，段落之间空一行。

# ［转载］英文Email

### 作者：白羽轩❤Queenie

Thank you for contacting us.如果有人写信来询问公司的服务，就可以使用这句句子开头。向他们对公司的兴趣表示感谢。

Thank you for your prompt reply.当一个客户或是同事很快就回复了你的邮件，一定记得要感谢他们。如果回复并不及时，只要将“prompt”除去即可，你还可以说，“Thank you for getting back to me.”

Thank you for providing the requested information.如果你询问某人一些信息，他们花了点时间才发送给你，那就用这句句子表示你仍然对他们的付出表示感激。

Thank you for all your assistance.如果有人给了你特别的帮助，那一定要感谢他们！如果你想对他们表示特别的感激，就用这个句子，“I truly appreciate … your help in resolving the problem.”Thank you raising your concerns.

Thank you for your kind cooperation.如果你需要读者帮助你做某事，那就先得表示感谢。

Thank you for your attention to this matter.与以上的类似，本句包含了你对对方将来可能的帮助表示感谢。

Thank you again for everything you’ve done.这句句子可以用在结尾，和以上有所不同。如果你在邮件开头已经谢过了读者，你就可以使用这句话，但是因为他们的帮助，你可以着重再次感谢你们的付出。

1. Greeting message 祝福

Hope you have a good trip back. 祝旅途愉快。

How are you? 你好吗?

How is the project going? 项目进行顺利吗?

2. Initiate a meeting 发起会议

I suggest we have a call tonight at 9:30pm (China Time) with you and Brown. Please let me know if the time is okay for you and Ben.

I would like to hold a meeting in the afternoon about our development planning for the project A.

We’d like to have the meeting on Thu Oct 30. Same time.

Let’s make a meeting next Monday at 5:30 PM SLC time.

I want to talk to you over the phone regarding issues about report development and the XXX project.

Should you have any problem accessing the folders, please let me know.

Thank you and look forward to having your opinion on the estimation and schedule.

Look forward to your feedbacks and suggestions soon.

What is your opinion on the schedule and next steps we proposed?

Any question, please don’t hesitate to let me know.

Any question, please let me know.

Please let me know if you have any question on this.

Please let me know what you think?

It would be nice if you could provide a bit more information on the user’s behavior.

At your convenience, I would really appreciate you looking into this matter/issue.

4. Give feedback 意见反馈

My answers are in blue below.

5. Attachment 附件

I enclose the evaluation report for your reference.

Attached please find today’s meeting notes.

Attach is the design document, please review it.

For other known issues related to individual features, please see attached release notes.

6. Point listing 列表

Today we would like to finish following tasks by the end of today:1…….2…….

Some known issues in this release:1…….2…….

Our team here reviewed the newest SCM policy and has following concerns:1…….2…….

Here are some more questions/issues for your team:1…….2…….

The current status is as following: 1……2……

7. Raise question 提出问题

I have some questions about the report XX-XXX

For the assignment ABC, I have the following questions:…

8. Proposal 提议

For the next step of platform implementation, I am proposing…

I suggest we can have a weekly project meeting over the phone call in the near future.

Achievo team suggest to adopt option A to solve outstanding issue……

Achievo团队建议应对突出问题采用A办法。

9. Thanks note 感谢信

Thank you so much for the cooperation感谢你的合作!

Thanks for the information

I really appreciate the effort you all made for this sudden and tight project.

Your kind assistance on this are very much appreciated.

10. Apology 道歉

I sincerely apologize for this misunderstanding!

I apologize for the late asking but we want to make sure the correctness of our implementation ASAP.

# 【南京大学新加坡校友会】迎新活动之新老生交流会

2014年7月27日在utown的ERC的meeting room 10，对刚来新加坡国立大学和南洋理工的南京大学同学做了一个关于NUS的硕博连读的一个小报告。

# Marina Bay Sands, 金沙酒店

2013年11月16日，去传说中的金沙酒店游泳池逛了一圈。为了同时看到白天的景色和晚上的景色，选择了从下午4点到晚上8点。如果入住金沙酒店的话，可以提前45天左右预定，貌似打折不少。只要入住了金沙酒店，就可以去上面的游泳池，并且在游泳的同时观光。游泳池位于55楼层高的塔楼楼顶，长度大概198米。

天色彻底暗了下来，新加坡的夜景真的很美。除了Marina Bay Sands上面，从摩天轮上面往下看也是不错的景色。  游泳池旁边就是一些餐厅之类的，饿了可以点一些饮料或者食物。 夜晚躺在这里的躺椅上看夜景很赞。水里面有照明灯。

# North Tower, Level 22 (Non-Air Condition) : From 15 July, 2014 to

Utown的房子和PGPR的不一样，一个屋子里面有四个房间，每个房间住一个人，大家共用卫生间和客厅，所以遇到好的室友就比较重要了。客厅里面理论上不让别人入住，如果有人入住并且被发现的话，那么宿舍里面的四个人都要被宿舍管理员赶走，而且在校期间恐怕都不能够继续入住学校宿舍了。

Bedroom: 高层的卧室不错，视野也比较开阔，单人床一张，桌子一个，床边的那两扇活叶窗可以转开。

Bookshelf：书架和衣柜各一个，可以放不少的东西。并且有一个可以活动的小型床头柜。

Living Room：客厅沙发两张，鞋柜一个，冰箱一个，微波炉一个，虽然不能够烧饭，但是用微波炉加热东西还是可以的。

Wash Room：卫生间和淋浴室各一个，洗手池两个。

the view out of the window：窗户外面的风景不错，直接可以看到CREATE的建筑，看到操场和游泳池，远一点都可以看到理学院。

Laundry Room in Level 2, North Tower：南楼和北楼各一个洗衣房，都在二楼。洗衣房里面有洗衣机和烘干机，每用一次洗衣机和烘干机都是一块钱。不过只能够用第三代的一块钱硬币，如果没有硬币的话，可以用里面的换硬币机器，使用纸币换硬币。里面还有一些衣架，可以用来晾衣服。饮水机也有一个，挺方便的。

the small garden in utown residence：南楼和北楼里面都有一个很小的花园，风景不错，也有一些座位给大家坐。有一些楼层，比方说8楼，22楼，都有一些小的平台，8楼的平台直接就是空中的一个小花园。有的时候晚上和朋友们在平台上面聊天啥的，风景不错。

Education Resource Centre (ERC)：一楼外面有一些白色的座位，附近也有无线的Wifi，可以坐在这里自习或者小组讨论。一楼有一个星巴克，开学的时候都是24小时开的，随时都可以去买咖啡和蛋糕。

Meeting Room in ERC：在ERC的二楼，有一些给学生答疑的小教室。MA1505和MA1506的答疑地点已经从工程学院的小屋子移到了ERC里面的小教室，小教室里面还有一个电视机。有这个电视机就可以链接自己的个人电脑，可以放自己的幻灯片，做一个小型的报告。不过如果要使用这些教室的时候，是需要在网上面提前预定的。

MacRoom in ERC：进门的时候需要刷学生卡。里面全部是iMac，用NUS的ID和密码就可以登录，随便使用。可惜鼠标并不是mac的，可能是考虑到有的人不适应那个鼠标，所以还是使用一般的鼠标。

# (zz) How to leave academia

So you’ve decided to leave academia, or are perhaps just thinking about doing so. Welcome to the dark side. I made the transition a few years ago, and since then I’ve gotten a number of questions about how to do it. Hence, this article.

First of all, I’m going to assume you are looking for a technical job, and I’m also going to assume you are coming from a technical field. When I left my postdoc I focused on finding jobs in technology and in finance.

A number of people seem happy about leaving academia and doing consulting (e.g. McKinsey), but I don’t know anything so I won’t comment. Also, if your degree is in English, the best I can do is point you here.

Good news – you’ve already got a solid quantitative background. This opens up a lot of doors for you. Now you just need to focus on building up some practical skills. They are a lot easier than algebraic geometry or solid state physics, but they are necessary nonetheless.

### Programming

Most jobs open to quantitative people these days involve programming, so it’s strongly beneficial for you to learn it.

To begin with, go read Software Carpentry. Right now. This document covers all the basic practicalities of dealing with code. Even if you plan to stay in academia, you should go read it, particularly if you plan to be a computational scientist. I’d differ from software carpentry in only one case: use git instead of subverson. A tutorial on git can be found here.

As far as programming languages to learn, I’d suggest Python to start with. This is because python has the excellent scientific Python and matplotlib libraries, which matlab like functionality in a language suitable for use at work. You should also learn C++ – it’s fairly widely used in quantitative jobs, particularly in finance. It’s also very common for interviewers to ask C++ questions even if the job uses another language. I found the book Practical C++ Programminghelpful, at least to reach a practical level.

For C++, I have yet to find a better first book than ‘Accelerated C++’ by Koenig and Moo. Lots of good books after that, but that one is one of the few textbooks in any field that I would feel enthusiastic handing to a beginner.

The key fact to note about coding is that the goals are different in academia and out. In academia, the end product is a publication and your code needs to work only once. After the important graph/image is generated and included in latex, you are finished. Outside academia the end product is usually software and it needs to work reliably. This involves a very different coding style – for example, instead of observing garbage output and rerunning the program, your program needs to automatically detect errors and either fix them or notify the user. Learn to develop this coding style early, it will help you later on.

It’s important to learn about algorithms. One of the classic books is Introduction to Algorithms (it’s the one on my desk right now), but there are many more. Also, algorithm questions come up often on job interviews.

Frederick Ross also suggested

For algorithms, Skiena’s ‘The Algorithm Design Manual’ is a bit quicker to get up to speed than Cormen (though Cormen is gorgeous). I don’t feel as strongly about this.

Another important skill is web development, for two reasons. One is that the web is becoming a universal front end to computers. The other is that if you write a cool webapp, you can show it off to potential employers. I’d recommend learning Django, due solely to the fact that you are already going to learn Python in order to use Scipy. The free Django Book is a great place to get started.

If you don’t like Python, Ruby on Rails is another option. From what I can see, you can’t go wrong choosing either Rails or Django. The only reason I suggest Python over Ruby is that Ruby doesn’t have anything comparable to Scipy.

#### Focus on Practicalities

A lot of academics focus primarily on core concepts of computing. This is a very good idea, but you must not neglect the practical aspects.

To find a list of phone numbers in a file, a smart man writes observes that phone numbers form a regular language and writes an optimized finite state automaton in C++. A wise man knows that grep already exists, and types:

grep "[0-9]\{3\}[-]\?[0-9]\{3\}[-]\?[0-9]\{4\}" filename.txt


If I run into a smart man on a job interview, I’ll tell him to reapply when he becomes wise. Many of the hard problems in computing are already solved. In both work and job interviews, it’s very important not to reinvent the wheel.

#### Data Science

The most accessible job to a typical physicist cum programmer goes by the job title Data Scientist. It’s also one of the more high paying jobs in technology. Probably the best way to describe the job is “be the programmer who understands regression and confidence intervals”.

Nowadays, businesses generate a lot of data. A single user browsing a website can generate 20-30 data points in a few minutes – click data, scroll data, pause data (the user paused to look at something), etc. The job of the data scientist is to look for patterns in this data and come up with useful ways of explaining it to technical and non-technical people. For example, at Styloot, I analyzed data to determine which properties of a dress are considered important by women (and used this to build a search engine for clothing).

To do this job you need to be a good programmer. You also need some basic statistics and machine learning skills. The classic introduction to machine learning is Pattern Recognition and Machine Learning, by Bishop. A basic intro to statistics is Data Analysis: A Bayesian Tutorial by Sivia and Skilling, a more advanced intro is Bayesian Data Analysis by Gelman. Of course, whatever you used in grad school is probably also sufficient.

For small data sets (2-8GB) you can write code using python and numpy, and this will cover many important applications. For larger data sets, Hadoop seems to be the standard tool. Hadoop is quite heavyweight, however, so don’t start off with it.

### Finance

The starting point for learning finance is learning the basics of pricing derivatives. The classic starting point is Wilmott’s Book. Another somewhat more sophisticated book is An Introduction to the Mathematics of Financial Derivatives. The key takeaways from these books are Gaussian models, Black-Scholes, PDE models and Monte-Carlo simulation.

#### Finance Interviews

Interviewing at financial institutions is a skill in itself and it’s one you need to get good at. For the most part, you can expect to be asked basic programming questions, basic questions on quantitative finance, as well as brainteasers involving basic probability:

Consider the integers from [0,1000]. Suppose a particle starts at position n. At discrete instants of time t=0,1,2,…, the particle moves up or down with p=0.5. What is the probability that the particle reaches 0 before t=1000?

100 passengers have queued up to board a plane, and are lined up in the order of the seats on the plane (n=1..100). However, the first person lost his ticket and selects a random seat. The remaining passengers will occupy their assigned seat if it is available, or a random seat otherwise. What is the probability that passenger 100 sits in seat 100?

The source of hundreds of such brainteasers is Heard on the Street. In addition to giving great interview practice, many lazy/busy interviewers take questions directly from this book.

The best way to get good at interviews is to practice interviewing. I recommend that you start doing finance interviews a year or two before you graduate, just so you have some under your belt and are good at them.

### Other Niches

In addition to general quant development and finance, there are a variety of other niches where quant Ph.D.’s do well.

If you are American, many military or other government contractors will hire you for physics and behavioral modelling. Typical jobs here might involve modelling the spread of disease, radio interference between different communication devices, cryptography or game theory. I have no firsthand experience, but I’m told these jobs are usually very stable, very bureaucratic and political, and are typically located just outside major metro areas (the sole exception being DC). One notable exception is Palantir which allegedly behaves a lot like a tech company, though a significant fraction of the engineers they hire wind up working in sales jobs.

Another niche is biostatistics. I don’t know much about it, but people with a solid stats background often wind up there.

There are also a variety of small tech companies selling specific scientific products to larger institutions. These will often be things like face recognition, LIDAR systems, sensor networks, statistical software, telecom or environmental modelling. The culture at these places varies widely – some behave like Valley startups, others act like government contractors.

## Finding a Job

First of all, don’t just send out your academic CV. Shorten it to a resume. The resume shouldn’t be more than 1-2 pages long. It should focus on your skills and what you’ve done and can do. Your education should probably be at the top, and your publications/talks should probably be last. After you’ve had 1-2 jobs, your experience should be at the top, followed by skills, followed by education, and maybe you’ll still bother to include publications. Here is my old academic CV and my current resume.

If you are looking for work in a programming job, it’s very helpful to build a portfolio. A github account with a few projects is helpful, as is a publicly visible webapp. Some interesting projects and a well populated github will get you far more callbacks than a resume. I’ve gotten quite a few job interviews without ever writing a resume, based solely on the strength of publicly visible projects.

Another important point is how to market yourself. You want to focus on the value created rather than the specific methods. As if often the case, Patrick McKenzie wrote a great blog post on this topic.

In finance, pedigree is very important. If you went to Harvard for undergrad and UCLA for your Ph.D., emphasize your Harvard degree. Signalling is the name of the game here, and a github will be less helpful than in technology.

### Interviewing – it’s a skill

In technology, just convince the interviewer that you are smart and can get things done. Convincing them of cultural fit is also a good thing – if you want documentation and procedure at a startup, you won’t be very happy, and neither will anyone else.

One significant tip, particularly for phone interviews – don’t go silent. Tell me what you are thinking even if it’s wrong. It’s much better to sound like you are thinking than like you’ve given up.

Apart from that, I’ll just link to good blog posts on the topic:

How to take control of your job interview

From the other side – advice given to interviewers:

My Favorite Interview Question

### Networking

It’s important. I suck at it. The gist is to get out there, meet people, and try to help them out.

After posting this, I received some helpful info from Tim Hsiau. Both links look more or less spot on to me:

For networking, local meetups on topics people care about may exist. Personally, I’ve found that talking to former high school classmates was an excellent way of networking, but I guess YMMV depending on the quality of the cohort… In some ways, I think it’s a bit like dating. You have to find out where the decision makers/girls are, and then demonstrate value to get them to pay attention.

This blog might have some interesting info, although it might be aimed towards more established professionalshttp://www.socalcto.com/2009/10/visible-networking.html http://www.socalcto.com/2009/10/marketing-startups-and-networking-in.html

### Salary Negotiation

(I’m also sick of linking to him, but his blog is great.)

## What it’s actually like

Once you actually get a job, things are a bit different. In academia, half the goal is to show how smart you are. The end goal is to have a grand unified theory of whatever, which is simple, elegant and beautiful. The problems you solve should be as general as possible. Code is written to get a single graph, attach it to the paper, and submit. The end product is publications and grants.

In the outside world, the goal is to give customers something in return for money. This won’t necessarily be a testament to your genius – the customers don’t care if you use cheap tricks to avoid solving the fundamental problem. You can build Strong AI or just run a call center in India – your customers don’t care about those details, they just care about you solving their problems. Cheap hacks are just as good as grand theorems.

Much like in academia, some of the work you do will be the fun work you signed up for, and some of it will be boring grunt work. As a postdoc, I found teaching and writing papers to be boring. As a startup CTO, I find writing web scrapers and building crud apps to be similarly boring. You can’t avoid this, all you can do is change the form it takes.

One of the biggest differences between academia and industry is the ranking system. Academia is a tournament – either you make it to the top or you are nobody. Once you prove the full theorem, there is little interest in special cases. In industry there is plenty of room for B-players and there is lots of interest in yet another CRUD app or a new application of linear regression.

Further discussion on this topic can be found on Hacker News.

In particular, note eli_gottlieb’s post discussing why he doesn’t like working in industry. Definitely required reading.

Disclaimer: Links to books are affiliate links. If you click the link and buy the book, I’ll get a buck or two. You can tweak the urlparams if you want to change this. To keep myself honest, I restricted my list of books to those I either owned or borrowed myself unless otherwise noted.

# 你看到的都是招数，不是内功（文/王路）

2013-01-30 22:23:15

# 【转载】一篇旧文—–史小杰

### 一篇旧文 公开 2014-04-09 10:35 |(分类:默认分类)

晚上无意翻到去年给杂志敲的一篇文章。原文敲了5800字，最后编辑截取了约2800字刊登于《读者 原创版》2013年第10期。想到去年离开新加坡的时候才想到自己对这个国家的历史了解甚少，于是跑去书店买了两大本《李光耀回忆录》匆匆读完。发出来权当介绍岛国吧。人生无数次告别，希望每一次都可以留下一点回声。

“城在花园中”–狮城因绿化闻名，蓬勃生长的热带树木功不可没。在阳光灿烂雨水充沛的赤道，防止植被生长过快才是课题。街头常见的是工人站在升降台上砍去树木侧枝，或三五一伙包裹严实修剪草坪。倘有人路过，便关上电锯割草机让行人先走，运气好的时候双方互送一个微笑。

“新加坡很多人都是从当年大陆东南沿海逃来的渔民的后代，没有文化，有的没法生存；大陆人是中原文化那些儒家秀才、达官贵人的后代；你们有条件比我们搞得好。”改革开放伊始，李光耀一次谈到新加坡的治理时这样对邓小平说。而对面是良久的沉默。

“你们都是人才，希望你们将来有机会能回去报效祖国。”你可曾试过这样的感觉，深夜挤在末班校车上，在一群为了论文或买房头痛的年轻人中，带着挣扎在底层的穷学生不见未来的忧郁，被一位中国司机当头棒喝的感觉。一瞬间又仿佛听到了幼年时才有的报效祖国的教诲。这一切竟是出自一位没有读过太多书的校车司机，多么有趣。

2007年末，我在北京机场送机处将厚厚的冬衣脱给父母，不忘抹去几滴初次出远门的泪水，便匆忙登机一路向南。几个小时后初识的狮城以它夏夜的气温给了我一个热情的拥抱。记得那时航空发动机造成的耳鸣尚未过去，但依然可以听清前面入关的女生好意提醒我咽口水以对抗耳鸣。

# 庾信平生最萧瑟，暮年诗赋动江关

2013-12-22 15:05:47

# 庾信平生最萧瑟，暮年诗赋动江关

“日暮途远，人间何世？将军一去，大树飘零；壮士不还，寒风萧瑟。荆璧睨柱，受连城而见欺；载书横阶，捧珠盘而不定。钟仪君子，入就南冠之囚；季孙行人，留守西河之馆。申包胥之顿地，碎之以首；蔡威公之泪尽，加之以血。钓台移柳，非玉关之可望；华亭鹤唳，岂河桥之可闻？”

“且夫天道回旋，生民赖焉。余烈祖于西晋，始流播于东川。洎余身而七叶，又遭时而北迁。提挈老幼，关河累年。死生契阔，不可问天。况复零落将尽，灵光岿然！日穷于纪，岁将复始。逼切危虑，端忧暮齿。践长乐之神皋，望宣平之贵里。渭水贯于天门，骊山回于地市。幕府大将军之爱客，丞相平津侯之待士。见钟鼎于金张，闻弦歌于许史。岂知灞陵夜猎，犹是故时将军；咸阳布衣，非独思归王子！”

2013年12月17日有感

# PHD期间看过的电视剧：

## 美剧：

The Vampire Diaries：

# 作者： 李博文

“在此时刻，我认为当初的决定下得是草率的，事后的发展完全没有预计，感谢一些朋友事前的忠告。国内学术圈的现实：残酷、无信、无情。虽然因我的自以为是而忽视。”

The finity can’t comprehend the infinity.

xmmxmu最近有一条微博：“我渐渐开始意识到，我这辈子极有可能成不了富二代他爹官二代他爹，只能当一个平凡的我娃他爹了。。。每每想到这里，我就觉得眼前的生活开阔亮丽了不少。”

David呆回复他说：“有时候觉得接受自己终将平庸的事实也算是成熟的表现啊。”

“今年是龙年，我依然用着这传了五千年的宝贵文字纪录我的人生。在我生日之际，我真心希望所有龙的传人能够睁开双眼，看看我们所面对的真实世界，客观地分析一下我们民族的未来在哪里。”