一切从简，简单就是幸福快乐。
物质上不在乎拥有多少，重要的是心灵富足。
Saturday, December 29, 2007
Thursday, December 27, 2007
成熟的人是要改變自己來面對自己的問題
一次在美國哈佛大學聽了一場演講，題目是如何做一個成熟的人，聽完以
後感慨良多啊！
原本以為自己很成熟，後來才知道原來自己還是不成熟的。 他的第一句話
說：「 成熟的人是要改變自己來面對自己的問題 」。
想想看在你週遭的家人朋友愛人中誰會去改變自己，不管改多改少，如果
有在改，你將會發現他遇到了困難越來越少，處理事情越來越得心應手，
自然就會散發出成熟的魅力。
回想一下小孩子的行為模式，今天他要到一顆糖，他用的方法是吵鬧哭，
他絕對不會想到把自己變的乖一點就有糖吃，各位想想看，你是否有一些
觀念是錯誤的，違背了社會風俗而你卻不願去改變，只用一些藉口說，那
是根深蒂固的思想，所以沒辦法改，那你跟小孩子的行為有什麼不同呢，
你自己根本沒資格去衡量別人成不成熟。
因為別人至少有在改，只是慢了一點 ，你不能因為別人的學歷和生活的
環境不同，就認為他不成熟，或許他做錯了事，觀念錯了都肯去修改，而
你呢？？
曾經有位學生在上課中問我說，她和她的男友已交往一兩年了，不過，她
發現她男朋友好像進步很慢，好像都是她在拉拔他，所以她要和她分手，
不過，他男朋友這時才振作起來決定要努力，那位同學問我說，那我是不
是要繼續和他在一起，因為，我覺得他好不成熟喔！
我只對他說，如果，妳這時候離開他是最不成熟的表現，因為，你們都遇
到了困難，而妳卻把難題留下來給他一個人，自己就像鴕鳥一樣的躲開，
所以，我建議妳在這時候要幫他成長，在現在這種情況下，妳的一句獎勵
的話，妳的陪伴，妳的愛，都勝過其他人的一百倍一千倍，一個人好不容
易有想改想變的念頭，那只是剛開始燃燒的火，如果妳這時候離他而去，
那就像拿一桶水把火澆熄了。如果，妳要離開他應該是他有成就時才離
開，這樣才是成熟的表現，不過，我想妳這時候也不會想離開他吧？！
五年後那個學生回來謝謝我，當初要不是聽了我的話，他現在也不會是某
年輕企業家的老婆了，又有一次我在路上遇到一位搭便車了的少女，看她
上車後紅著雙眼，我問她：「小姐妳沒事吧。」她卻哭了出來，說他剛和老
公辦完了離婚手續，因是太多觀念不一樣，我就跟她說，在美國做過一項
調查，婚姻生活到 60歲還維持美滿的夫妻中，有99%他們的另一半，不是
合乎當初他們心目中的人選，理念多半不相同，而且幾乎都是其中一個愛
另一個多，我問他們，那為什麼婚姻還能美滿的維持呢？
他們說，如果遇到理念不同時，就是要提出來互相討論，而不是爭論，而
且，要在適當的時機，例如約會時，洗澡時，做愛時都是很好的時機，而
雙方都要去改，不能堅持己見，明明是錯誤的觀念不去改，說什麼已經根
深蒂固之類的話，哪只是逃避，是很不成熟的行為。
所以，我跟她說天下沒有完全相和的人，牙齒都會咬到舌頭了，何況是
兩個成長在不同環境的人的人呢？ 所以，妳要努力改變自己來適應他，他
也要努力的改變自己來適應妳，不管是誰只要有錯的觀念就要改知道嗎？
三年後在一場演講會的後台，再次遇到那位女子，她來謝謝我，說她那天
回家後，馬上打電話給老公，把我的話說給他聽，現在，他們已經又結婚
了三年有兩個小寶寶，生活上都沒有衝突，沒想到當初那麼不合的兩個
人，現在生活卻很美滿。
各位朋友想想看你是不是有這些缺點呢，妳夠不夠成熟？！要罵別人不
成熟時，要先想想自己喔！
後感慨良多啊！
原本以為自己很成熟，後來才知道原來自己還是不成熟的。 他的第一句話
說：「 成熟的人是要改變自己來面對自己的問題 」。
想想看在你週遭的家人朋友愛人中誰會去改變自己，不管改多改少，如果
有在改，你將會發現他遇到了困難越來越少，處理事情越來越得心應手，
自然就會散發出成熟的魅力。
回想一下小孩子的行為模式，今天他要到一顆糖，他用的方法是吵鬧哭，
他絕對不會想到把自己變的乖一點就有糖吃，各位想想看，你是否有一些
觀念是錯誤的，違背了社會風俗而你卻不願去改變，只用一些藉口說，那
是根深蒂固的思想，所以沒辦法改，那你跟小孩子的行為有什麼不同呢，
你自己根本沒資格去衡量別人成不成熟。
因為別人至少有在改，只是慢了一點 ，你不能因為別人的學歷和生活的
環境不同，就認為他不成熟，或許他做錯了事，觀念錯了都肯去修改，而
你呢？？
曾經有位學生在上課中問我說，她和她的男友已交往一兩年了，不過，她
發現她男朋友好像進步很慢，好像都是她在拉拔他，所以她要和她分手，
不過，他男朋友這時才振作起來決定要努力，那位同學問我說，那我是不
是要繼續和他在一起，因為，我覺得他好不成熟喔！
我只對他說，如果，妳這時候離開他是最不成熟的表現，因為，你們都遇
到了困難，而妳卻把難題留下來給他一個人，自己就像鴕鳥一樣的躲開，
所以，我建議妳在這時候要幫他成長，在現在這種情況下，妳的一句獎勵
的話，妳的陪伴，妳的愛，都勝過其他人的一百倍一千倍，一個人好不容
易有想改想變的念頭，那只是剛開始燃燒的火，如果妳這時候離他而去，
那就像拿一桶水把火澆熄了。如果，妳要離開他應該是他有成就時才離
開，這樣才是成熟的表現，不過，我想妳這時候也不會想離開他吧？！
五年後那個學生回來謝謝我，當初要不是聽了我的話，他現在也不會是某
年輕企業家的老婆了，又有一次我在路上遇到一位搭便車了的少女，看她
上車後紅著雙眼，我問她：「小姐妳沒事吧。」她卻哭了出來，說他剛和老
公辦完了離婚手續，因是太多觀念不一樣，我就跟她說，在美國做過一項
調查，婚姻生活到 60歲還維持美滿的夫妻中，有99%他們的另一半，不是
合乎當初他們心目中的人選，理念多半不相同，而且幾乎都是其中一個愛
另一個多，我問他們，那為什麼婚姻還能美滿的維持呢？
他們說，如果遇到理念不同時，就是要提出來互相討論，而不是爭論，而
且，要在適當的時機，例如約會時，洗澡時，做愛時都是很好的時機，而
雙方都要去改，不能堅持己見，明明是錯誤的觀念不去改，說什麼已經根
深蒂固之類的話，哪只是逃避，是很不成熟的行為。
所以，我跟她說天下沒有完全相和的人，牙齒都會咬到舌頭了，何況是
兩個成長在不同環境的人的人呢？ 所以，妳要努力改變自己來適應他，他
也要努力的改變自己來適應妳，不管是誰只要有錯的觀念就要改知道嗎？
三年後在一場演講會的後台，再次遇到那位女子，她來謝謝我，說她那天
回家後，馬上打電話給老公，把我的話說給他聽，現在，他們已經又結婚
了三年有兩個小寶寶，生活上都沒有衝突，沒想到當初那麼不合的兩個
人，現在生活卻很美滿。
各位朋友想想看你是不是有這些缺點呢，妳夠不夠成熟？！要罵別人不
成熟時，要先想想自己喔！
Saturday, December 22, 2007
致富营业良规 -- 陶朱公
生意要勤紧，懒惰则百事废。
用度要节俭，奢侈则用途竭。
接纳要温和，躁暴则交易少。
买卖要随时，挨延则机宜失。
议价要订明，含糊则争执多。
赊欠要识人，滥出则血本亏。
账目要稽查，懒怠则资本滞。
优劣要分清，苟且则必糊涂。
货物要整理，散漫则必废残。
用人要方正，诡谲则受其累。
出纳要谨慎，大意则错漏多。
货物要面验，滥收则售价低。
期限要约定，延迟则信用失。
钱则要清楚，糊涂则弊窦生。
临事要责任，放弃则受害大。
主心要镇定，妄作则误事多。
事业兴隆以资良友，权衡操纵端赖法人。
用度要节俭，奢侈则用途竭。
接纳要温和，躁暴则交易少。
买卖要随时，挨延则机宜失。
议价要订明，含糊则争执多。
赊欠要识人，滥出则血本亏。
账目要稽查，懒怠则资本滞。
优劣要分清，苟且则必糊涂。
货物要整理，散漫则必废残。
用人要方正，诡谲则受其累。
出纳要谨慎，大意则错漏多。
货物要面验，滥收则售价低。
期限要约定，延迟则信用失。
钱则要清楚，糊涂则弊窦生。
临事要责任，放弃则受害大。
主心要镇定，妄作则误事多。
事业兴隆以资良友，权衡操纵端赖法人。
Monday, December 17, 2007
10 types of programmers you’ll encounter in the field 10种你会碰到的程序员
Programmers enjoy a reputation for being peculiar people. In fact, even within the development community, there are certain programmer archetypes that other programmers find strange. Here are 10 types of programmers you are likely to run across. Can you think of any more?
程序员素来就被认为是一个奇特的人群。实际上，就算在程序开发者社群本身之中，也有一些特别的人群能让其他程序员觉得很奇怪。在这我列出10种你可能遇到过的程序员，你能想出更多么？
#1: Gandalf
#1:甘道夫
This programmer type looks like a short-list candidate to play Gandalf in The Lord of the Rings. He (or even she!) has a beard halfway to his knees, a goofy looking hat, and may wear a cape or a cloak in the winter. Luckily for the team, this person is just as adept at working magic as Gandalf. Unluckily for the team, they will need to endure hours of stories from Gandalf about how he or she to walk uphill both ways in the snow to drop off the punch cards at the computer room. The Gandalf type is your heaviest hitter, but you try to leave them in the rear and call them up only in times of desperation.
这种程序员看起来，就像是在《指环王》里扮演甘道夫的最佳候选人。他（甚至是她）有着快要到膝盖的胡子，一顶看起来傻傻的帽子，在冬天可能还会穿一件披风或者是斗篷。对于团队来说幸运的是，此人对自己工作的熟练程度就像甘道夫一样。但不幸的是，他们要经常忍受甘道夫长达数个小时的故事的折磨，而内容主要是关于他或者是她是如何不得不在雪地中上山下山，以把打好孔的纸带送到计算机房。甘道夫类型的程序员是你的究极武器，但是你会总是希望能把他们排到后面，只在快要绝望的时候才向他们寻求帮助。
#2: The Martyr
#2:烈士
In any other profession, The Martyr is simply a “workaholic.” But in the development field, The Martyr goes beyond that and into another dimension. Workaholics at least go home to shower and sleep. The Martyr takes pride in sleeping at the desk amidst empty pizza boxes. The problem is, no one ever asked The Martyr to work like this. And he or she tries to guilt-trip the rest of the team with phrases like, “Yeah, go home and enjoy dinner. I’ll finish up the next three week’s worth of code tonight.”
对于任何其它职业来说，烈士其实就是一个工作狂而已。但是在开发者的领域，烈士完全进入了另外一个范畴。工作狂至少会回家洗澡睡觉，而烈士们却会以睡在桌子底下的空皮萨盒子堆之中为荣。而问题是，根本就没人要求烈士们像这样工作。而且他或者她总是想用这样的措辞来使团队中的其他人感到内疚，“好的，你们回家吃完饭吧。我会在今晚会完成相当于3个星期的工作量的。”
#3: Fanboy
#3:玩家
Watch out for Fanboy. If he or she corners you, you’re in for a three-hour lecture about the superiority of Dragonball Z compared to Gundam Wing, or why the Playstation 3 is better than the XB 360. Fanboy’s workspace is filled with posters, action figures, and other knick-knacks related to some obsession, most likely imported from Japan. Not only are Fanboys obnoxious to deal with, they often put so much time into the obsession (both in and out of the office) that they have no clue when it comes to doing what they were hired to do.
小心玩家。如果他或者是她注意到了你，你很有可能就要接受3至4个小时关于龙珠z与高达谁更强、或者是playstation 3 与xbox 360哪个更好的演讲。玩家的桌子上总是堆满了明信片、动作人偶、以及其他各种各样相关的装饰品，大部分可能都是从日本进口的。玩家们不光是很难相处，他们有的时候实在是太多时间在这些东西上（无论是在办公室内外），以至于他们根本就不明白他们什么时候该干老板雇他们做的工作。
#4: Vince Neil
#4:文斯 内尔(一个比较有名的摇滚歌手)
This 40-something is a throwback to 1984 in all of the wrong ways. Sporting big hair, ripped stonewashed jeans, and a bandana here or there, Vince sits in the office humming Bon Jovi and Def Leppard tunes throughout the workday. This would not be so bad if “Pour Some Sugar on Me” was not so darned infectious.
这个40岁的家伙就像是颠三倒四的回到了1984.运动型爆炸头，发皱泛白的牛仔裤，还有一条大围巾。文斯还会在工作时间坐在办公室哼着Bon Jovi 和 Def Leppard的歌，这本来也不是很糟，如果《Pour Some Sugar on Me》不是如此的有感染力的话。
Vince is generally a fun person to work with, and actually has a ton of experience, but just never grew up. But Vince becomes a hassle when he or she tries living the rock ‘n roll lifestyle to go with the hair and hi-tops. It’s fairly hard to work with someone who carries a hangover to work every day.
总体来说，和文斯一起工作是很有趣的，实际上他有丰富的经验，只是永远长不大而已。但是如果文斯决定用他或者是她的摇滚风格来处理自己的头发和生活的时候，情况就会变得很棘手。因为和一个每天都带着宿醉未醒的人一起工作，相当困难。
#5: The Ninja
#5:忍者
The Ninja is your team’s MVP, and no one knows it. Like the legendary assassins, you do not know that The Ninja is even in the building or working, but you discover the evidence in the morning. You fire up the source control system and see that at 4 AM, The Ninja checked in code that addresses the problem you planned to spend all week working on, and you did not even know that The Ninja was aware of the project! See, while you were in Yet Another Meeting, The Ninja was working.
忍者是你们团队当中的重要人物，但是却没人能意识到这点。就好象传奇刺客一样，你不知道忍者是什么时候工作的，但是你总是在第二天早晨发现他们的成果。于是你急忙打开源代码控制系统，然后发现在临晨4点，忍者提交了一份代码，解决了一个你已经研究了一个星期的问题，而你之前甚至都不知道忍者大人知道你所作的项目的存在。明白了吧，当你还在一次次的开会的时候，忍者一直在工作。
Ninjas are so stealthy, you might not even know their name, but you know that every project they’re on seems to go much more smoothly. Tread carefully, though. The Ninja is a lone warrior; don’t try to force him or her to work with rank and file.
忍者是如此的隐蔽，你甚至都不知道他们的名字，但是你知道每一个他们参与的项目都进行的更顺利。不过，注意点，忍者是孤胆战士，不要试图强迫他们在一个严格的等级和文档制度下工作。
#6: The Theoretician
#6:理论家
The Theoretician knows everything there is to know about programming. He or she can spend four hours lecturing about the history of an obscure programming language or providing a proof of how the code you wrote is less than perfectly optimal and may take an extra three nanoseconds to run. The problem is, The Theoretician does not know a thing about software development. When The Theoretician writes code, it is so “elegant” that mere mortals cannot make sense of it. His or her favorite technique is recursion, and every block of code is tweaked to the max, at the expense of timelines and readability.
理论家知道一切编程需要知道的东西。他或者是她可以花4个小时去探讨一个很冷僻的语言，或者去证明你写的代码是如何的不完美并且有可能会在运行的时候多花3纳秒。问题在于，理论家根本就不知道什么叫软件开发。当理论家写代码的时候，他的代码是如此的“优美”，以至于我们这些凡人根本就看不懂。他或者她最喜爱的技术就是递归，每一个代码块都被使用到了极致，而代价就是工程进度和可读性。
The Theoretician is also easily distracted. A simple task that should take an hour takes Theoreticians three months, since they decide that the existing tools are not sufficient and they must build new tools to build new libraries to build a whole new system that meets their high standards. The Theoretician can be turned into one of your best players, if you can get him or her to play within the boundaries of the project itself and stop spending time working on The Ultimate Sorting Algorithm.
理论家还很容易分心。一个花一个小时就能完成的工作，理论家们往往需要三个月。因为他们认为当前的开发工具不够好，所以他们必须开发一些新的工具来构建新的库从而构建一个全新的系统来迎合他们的高标准。理论家可以成为你最好的团队成员，前提是你能让他专注于你们所做的工程本身，而不是把时间都花在究极排序算法上。
#7: The Code Cowboy
#7:代码牛仔
The Code Cowboy is a force of nature that cannot be stopped. He or she is almost always a great programmer and can do work two or three times faster than anyone else. The problem is, at least half of that speed comes by cutting corners. The Code Cowboy feels that checking code into source control takes too long, storing configuration data outside of the code itself takes too long, communicating with anyone else takes too long… you get the idea.
代码牛仔是一种无法阻止的天性。他或者她几乎总是一个厉害的编程者，并且总是能以别人2至3倍的速度完成工作。问题是，这些代码至少有一半都靠偷工减料得来的。代码牛仔认为把代码提交到源码控制系统太麻烦，把配置信息存贮在代码之外太麻烦，和其它人交流太麻烦……你懂我的意思吧。
The Code Cowboy’s code is a spaghetti code mess, because he or she was working so quickly that the needed refactoring never happened. Chances are, seven pages’ worth of core functionality looks like the “don’t do this” example of a programming textbook, but it magically works. The Code Cowboy definitely does not play well with others. And if you put two Code Cowboys on the same project, it is guaranteed to fail, as they trample on each other’s changes and shoot each other in the foot.
代码牛仔的代码就好像意大利面条一样搅在一起，因为他或者她工作的事如此之快，以至于必要的重够都没有做到。很有可能的是，七页长的核心功能代码也许看起来就像是教科书上关于“不要这么做”的示例，而这些代码居然还神奇的可以运行。代码牛仔绝对没办法和别人一起工作。而且，如果你让两个代码牛仔进入同一个工程，那这个工程一定会失败，因为一个总是被另一个人对代码做的修改而干扰，他们总是拼命的在开枪射击自己搭档的脚。
Put a Code Cowboy on a project where hitting the deadline is more important than doing it right, and the code will be done just before deadline every time. The Code Cowboy is really just a loud, boisterous version of The Ninja. While The Ninja executes with surgical precision, The Code Cowboy is a raging bull and will gore anything that gets in the way.
当按时完成一个工程比把这个工程做好更重要的时候，把一个代码牛仔加入进去吧，这个工程会在截至日期之前完成的。代码牛仔其实就是一个吵闹版的忍者。只是忍者像做外科手术一样精准的编码，而代码牛仔像一只难以控制的公牛，会把所以挡在它面的东西顶翻。
#8: The Paratrooper
#8:伞兵
You know those movies where a sole commando is air-dropped deep behind enemy lines and comes out with the secret battle plans? That person in a software development shop is The Paratrooper. The Paratrooper is the last resort programmer you send in to save a dying project. Paratroopers lack the patience to work on a long-term assignment, but their best asset is an uncanny ability to learn an unfamiliar codebase and work within it. Other programmers might take weeks or months to learn enough about a project to effectively work on it; The Paratrooper takes hours or days. Paratroopers might not learn enough to work on the core of the code, but the lack of ramp-up time means that they can succeed where an entire team might fail.
你知道那些电影吧，就是指挥官带着机密作战计划被空降到敌人战线之后。在软件开发中，这样的人叫伞兵。伞兵是你对一个将要失败的工程的最后援助。伞兵们缺乏在一个长期任务上工作的耐心。他们最大的价值是拥有快速学习一堆完全陌生的代码并且使用它们工作的惊人能力。其他程序员也许要花几个星期或者其几个月来熟悉一个工程，以便可以有效的参与其中；伞兵们只需要几个小时或者几天。伞兵快速学会的东西也许不能让他们编写核心代码，但是，没有足够的时间形成一个固定的见解可能会帮助他在整个团队失败的地方取得成功。
#9: Mediocre Man
#9:庸才
“Good enough” is the best you will ever get from Mediocre Man. Don’t let the name fool you; there are female varieties of Mediocre Man too. And he or she always takes longer to produce worse code than anyone else on the team. “Slow and steady barely finishes the race” could describe Mediocre Man’s projects. But Mediocre Man is always just “good enough” to remain employed.
“足够好了”，这就是你从一个庸才那能听到的最好的话。他或者是她总是花更多的时间写出比团队中其他任何人都更差的代码。“缓慢，刚刚符合要求”就是对庸才所作的项目的描述。但庸才们总是能做的“足够好”，以至于刚好不会被解雇。
When you interview this type, they can tell you a lot about the projects they’ve been involved with but not much about their actual involvement. Filtering out the Mediocre Man type is fairly easy: Ask for actual details of the work they’ve done, and they suddenly get a case of amnesia. Let them into your organization, though, and it might take years to get rid of them.
当你面试这种人的时候，他可以告诉你很多他到参与过的项目，但却很少提到他们到底在这些项目里做了什么。筛出这些庸才的方法很简单：问一下他所做工作的细节，他们会突然得了健忘症。但是，一旦让这种人进入你的组织，你可能要花好几年才能再摆脱他们。
#10: The Evangelist
#10:传教士
No matter what kind of environment you have, The Evangelist insists that it can be improved by throwing away all of your tools and processes and replacing them with something else. The Evangelist is actually the opposite of The Theoretician. The Evangelist is outspoken, knows an awful lot about software development, but performs very little actual programming.
无论你在用哪种编程环境，传教士总会坚持认为如果你把现有的工具和工序抛弃掉并换成其它的一些东西，会对你有很大的帮助。传教士实际上就是理论家的反面。传教士总是直来直去，对软件开发很了解，但却很少真正的去编码。
The Evangelist is secretly a project manager or department manager at heart but lacks the knowledge or experience to make the jump. So until The Evangelist is able to get into a purely managerial role, everyone else needs to put up with his or her attempts to revolutionize the workplace.
传教士有一颗项目经理或者部门经理的心，但却缺乏足够的知识或者经验来完成这个跳跃。所以在传教士最终成为一个纯管理者角色之前，其他人不得不一直忍受传教士们对于彻底革新工作环境的尝试。
English Source
Chinese Translation Source
程序员素来就被认为是一个奇特的人群。实际上，就算在程序开发者社群本身之中，也有一些特别的人群能让其他程序员觉得很奇怪。在这我列出10种你可能遇到过的程序员，你能想出更多么？
#1: Gandalf
#1:甘道夫
This programmer type looks like a short-list candidate to play Gandalf in The Lord of the Rings. He (or even she!) has a beard halfway to his knees, a goofy looking hat, and may wear a cape or a cloak in the winter. Luckily for the team, this person is just as adept at working magic as Gandalf. Unluckily for the team, they will need to endure hours of stories from Gandalf about how he or she to walk uphill both ways in the snow to drop off the punch cards at the computer room. The Gandalf type is your heaviest hitter, but you try to leave them in the rear and call them up only in times of desperation.
这种程序员看起来，就像是在《指环王》里扮演甘道夫的最佳候选人。他（甚至是她）有着快要到膝盖的胡子，一顶看起来傻傻的帽子，在冬天可能还会穿一件披风或者是斗篷。对于团队来说幸运的是，此人对自己工作的熟练程度就像甘道夫一样。但不幸的是，他们要经常忍受甘道夫长达数个小时的故事的折磨，而内容主要是关于他或者是她是如何不得不在雪地中上山下山，以把打好孔的纸带送到计算机房。甘道夫类型的程序员是你的究极武器，但是你会总是希望能把他们排到后面，只在快要绝望的时候才向他们寻求帮助。
#2: The Martyr
#2:烈士
In any other profession, The Martyr is simply a “workaholic.” But in the development field, The Martyr goes beyond that and into another dimension. Workaholics at least go home to shower and sleep. The Martyr takes pride in sleeping at the desk amidst empty pizza boxes. The problem is, no one ever asked The Martyr to work like this. And he or she tries to guilt-trip the rest of the team with phrases like, “Yeah, go home and enjoy dinner. I’ll finish up the next three week’s worth of code tonight.”
对于任何其它职业来说，烈士其实就是一个工作狂而已。但是在开发者的领域，烈士完全进入了另外一个范畴。工作狂至少会回家洗澡睡觉，而烈士们却会以睡在桌子底下的空皮萨盒子堆之中为荣。而问题是，根本就没人要求烈士们像这样工作。而且他或者她总是想用这样的措辞来使团队中的其他人感到内疚，“好的，你们回家吃完饭吧。我会在今晚会完成相当于3个星期的工作量的。”
#3: Fanboy
#3:玩家
Watch out for Fanboy. If he or she corners you, you’re in for a three-hour lecture about the superiority of Dragonball Z compared to Gundam Wing, or why the Playstation 3 is better than the XB 360. Fanboy’s workspace is filled with posters, action figures, and other knick-knacks related to some obsession, most likely imported from Japan. Not only are Fanboys obnoxious to deal with, they often put so much time into the obsession (both in and out of the office) that they have no clue when it comes to doing what they were hired to do.
小心玩家。如果他或者是她注意到了你，你很有可能就要接受3至4个小时关于龙珠z与高达谁更强、或者是playstation 3 与xbox 360哪个更好的演讲。玩家的桌子上总是堆满了明信片、动作人偶、以及其他各种各样相关的装饰品，大部分可能都是从日本进口的。玩家们不光是很难相处，他们有的时候实在是太多时间在这些东西上（无论是在办公室内外），以至于他们根本就不明白他们什么时候该干老板雇他们做的工作。
#4: Vince Neil
#4:文斯 内尔(一个比较有名的摇滚歌手)
This 40-something is a throwback to 1984 in all of the wrong ways. Sporting big hair, ripped stonewashed jeans, and a bandana here or there, Vince sits in the office humming Bon Jovi and Def Leppard tunes throughout the workday. This would not be so bad if “Pour Some Sugar on Me” was not so darned infectious.
这个40岁的家伙就像是颠三倒四的回到了1984.运动型爆炸头，发皱泛白的牛仔裤，还有一条大围巾。文斯还会在工作时间坐在办公室哼着Bon Jovi 和 Def Leppard的歌，这本来也不是很糟，如果《Pour Some Sugar on Me》不是如此的有感染力的话。
Vince is generally a fun person to work with, and actually has a ton of experience, but just never grew up. But Vince becomes a hassle when he or she tries living the rock ‘n roll lifestyle to go with the hair and hi-tops. It’s fairly hard to work with someone who carries a hangover to work every day.
总体来说，和文斯一起工作是很有趣的，实际上他有丰富的经验，只是永远长不大而已。但是如果文斯决定用他或者是她的摇滚风格来处理自己的头发和生活的时候，情况就会变得很棘手。因为和一个每天都带着宿醉未醒的人一起工作，相当困难。
#5: The Ninja
#5:忍者
The Ninja is your team’s MVP, and no one knows it. Like the legendary assassins, you do not know that The Ninja is even in the building or working, but you discover the evidence in the morning. You fire up the source control system and see that at 4 AM, The Ninja checked in code that addresses the problem you planned to spend all week working on, and you did not even know that The Ninja was aware of the project! See, while you were in Yet Another Meeting, The Ninja was working.
忍者是你们团队当中的重要人物，但是却没人能意识到这点。就好象传奇刺客一样，你不知道忍者是什么时候工作的，但是你总是在第二天早晨发现他们的成果。于是你急忙打开源代码控制系统，然后发现在临晨4点，忍者提交了一份代码，解决了一个你已经研究了一个星期的问题，而你之前甚至都不知道忍者大人知道你所作的项目的存在。明白了吧，当你还在一次次的开会的时候，忍者一直在工作。
Ninjas are so stealthy, you might not even know their name, but you know that every project they’re on seems to go much more smoothly. Tread carefully, though. The Ninja is a lone warrior; don’t try to force him or her to work with rank and file.
忍者是如此的隐蔽，你甚至都不知道他们的名字，但是你知道每一个他们参与的项目都进行的更顺利。不过，注意点，忍者是孤胆战士，不要试图强迫他们在一个严格的等级和文档制度下工作。
#6: The Theoretician
#6:理论家
The Theoretician knows everything there is to know about programming. He or she can spend four hours lecturing about the history of an obscure programming language or providing a proof of how the code you wrote is less than perfectly optimal and may take an extra three nanoseconds to run. The problem is, The Theoretician does not know a thing about software development. When The Theoretician writes code, it is so “elegant” that mere mortals cannot make sense of it. His or her favorite technique is recursion, and every block of code is tweaked to the max, at the expense of timelines and readability.
理论家知道一切编程需要知道的东西。他或者是她可以花4个小时去探讨一个很冷僻的语言，或者去证明你写的代码是如何的不完美并且有可能会在运行的时候多花3纳秒。问题在于，理论家根本就不知道什么叫软件开发。当理论家写代码的时候，他的代码是如此的“优美”，以至于我们这些凡人根本就看不懂。他或者她最喜爱的技术就是递归，每一个代码块都被使用到了极致，而代价就是工程进度和可读性。
The Theoretician is also easily distracted. A simple task that should take an hour takes Theoreticians three months, since they decide that the existing tools are not sufficient and they must build new tools to build new libraries to build a whole new system that meets their high standards. The Theoretician can be turned into one of your best players, if you can get him or her to play within the boundaries of the project itself and stop spending time working on The Ultimate Sorting Algorithm.
理论家还很容易分心。一个花一个小时就能完成的工作，理论家们往往需要三个月。因为他们认为当前的开发工具不够好，所以他们必须开发一些新的工具来构建新的库从而构建一个全新的系统来迎合他们的高标准。理论家可以成为你最好的团队成员，前提是你能让他专注于你们所做的工程本身，而不是把时间都花在究极排序算法上。
#7: The Code Cowboy
#7:代码牛仔
The Code Cowboy is a force of nature that cannot be stopped. He or she is almost always a great programmer and can do work two or three times faster than anyone else. The problem is, at least half of that speed comes by cutting corners. The Code Cowboy feels that checking code into source control takes too long, storing configuration data outside of the code itself takes too long, communicating with anyone else takes too long… you get the idea.
代码牛仔是一种无法阻止的天性。他或者她几乎总是一个厉害的编程者，并且总是能以别人2至3倍的速度完成工作。问题是，这些代码至少有一半都靠偷工减料得来的。代码牛仔认为把代码提交到源码控制系统太麻烦，把配置信息存贮在代码之外太麻烦，和其它人交流太麻烦……你懂我的意思吧。
The Code Cowboy’s code is a spaghetti code mess, because he or she was working so quickly that the needed refactoring never happened. Chances are, seven pages’ worth of core functionality looks like the “don’t do this” example of a programming textbook, but it magically works. The Code Cowboy definitely does not play well with others. And if you put two Code Cowboys on the same project, it is guaranteed to fail, as they trample on each other’s changes and shoot each other in the foot.
代码牛仔的代码就好像意大利面条一样搅在一起，因为他或者她工作的事如此之快，以至于必要的重够都没有做到。很有可能的是，七页长的核心功能代码也许看起来就像是教科书上关于“不要这么做”的示例，而这些代码居然还神奇的可以运行。代码牛仔绝对没办法和别人一起工作。而且，如果你让两个代码牛仔进入同一个工程，那这个工程一定会失败，因为一个总是被另一个人对代码做的修改而干扰，他们总是拼命的在开枪射击自己搭档的脚。
Put a Code Cowboy on a project where hitting the deadline is more important than doing it right, and the code will be done just before deadline every time. The Code Cowboy is really just a loud, boisterous version of The Ninja. While The Ninja executes with surgical precision, The Code Cowboy is a raging bull and will gore anything that gets in the way.
当按时完成一个工程比把这个工程做好更重要的时候，把一个代码牛仔加入进去吧，这个工程会在截至日期之前完成的。代码牛仔其实就是一个吵闹版的忍者。只是忍者像做外科手术一样精准的编码，而代码牛仔像一只难以控制的公牛，会把所以挡在它面的东西顶翻。
#8: The Paratrooper
#8:伞兵
You know those movies where a sole commando is air-dropped deep behind enemy lines and comes out with the secret battle plans? That person in a software development shop is The Paratrooper. The Paratrooper is the last resort programmer you send in to save a dying project. Paratroopers lack the patience to work on a long-term assignment, but their best asset is an uncanny ability to learn an unfamiliar codebase and work within it. Other programmers might take weeks or months to learn enough about a project to effectively work on it; The Paratrooper takes hours or days. Paratroopers might not learn enough to work on the core of the code, but the lack of ramp-up time means that they can succeed where an entire team might fail.
你知道那些电影吧，就是指挥官带着机密作战计划被空降到敌人战线之后。在软件开发中，这样的人叫伞兵。伞兵是你对一个将要失败的工程的最后援助。伞兵们缺乏在一个长期任务上工作的耐心。他们最大的价值是拥有快速学习一堆完全陌生的代码并且使用它们工作的惊人能力。其他程序员也许要花几个星期或者其几个月来熟悉一个工程，以便可以有效的参与其中；伞兵们只需要几个小时或者几天。伞兵快速学会的东西也许不能让他们编写核心代码，但是，没有足够的时间形成一个固定的见解可能会帮助他在整个团队失败的地方取得成功。
#9: Mediocre Man
#9:庸才
“Good enough” is the best you will ever get from Mediocre Man. Don’t let the name fool you; there are female varieties of Mediocre Man too. And he or she always takes longer to produce worse code than anyone else on the team. “Slow and steady barely finishes the race” could describe Mediocre Man’s projects. But Mediocre Man is always just “good enough” to remain employed.
“足够好了”，这就是你从一个庸才那能听到的最好的话。他或者是她总是花更多的时间写出比团队中其他任何人都更差的代码。“缓慢，刚刚符合要求”就是对庸才所作的项目的描述。但庸才们总是能做的“足够好”，以至于刚好不会被解雇。
When you interview this type, they can tell you a lot about the projects they’ve been involved with but not much about their actual involvement. Filtering out the Mediocre Man type is fairly easy: Ask for actual details of the work they’ve done, and they suddenly get a case of amnesia. Let them into your organization, though, and it might take years to get rid of them.
当你面试这种人的时候，他可以告诉你很多他到参与过的项目，但却很少提到他们到底在这些项目里做了什么。筛出这些庸才的方法很简单：问一下他所做工作的细节，他们会突然得了健忘症。但是，一旦让这种人进入你的组织，你可能要花好几年才能再摆脱他们。
#10: The Evangelist
#10:传教士
No matter what kind of environment you have, The Evangelist insists that it can be improved by throwing away all of your tools and processes and replacing them with something else. The Evangelist is actually the opposite of The Theoretician. The Evangelist is outspoken, knows an awful lot about software development, but performs very little actual programming.
无论你在用哪种编程环境，传教士总会坚持认为如果你把现有的工具和工序抛弃掉并换成其它的一些东西，会对你有很大的帮助。传教士实际上就是理论家的反面。传教士总是直来直去，对软件开发很了解，但却很少真正的去编码。
The Evangelist is secretly a project manager or department manager at heart but lacks the knowledge or experience to make the jump. So until The Evangelist is able to get into a purely managerial role, everyone else needs to put up with his or her attempts to revolutionize the workplace.
传教士有一颗项目经理或者部门经理的心，但却缺乏足够的知识或者经验来完成这个跳跃。所以在传教士最终成为一个纯管理者角色之前，其他人不得不一直忍受传教士们对于彻底革新工作环境的尝试。
English Source
Chinese Translation Source
累了，就把心事放下來
最近認識一位美國籍的出家師父，是個很有趣的事情。
特別是他叫我舉起蕃茄汁跟他說話 的經驗。
我們約在新竹的一家茶館用英文談論著心經，
師父用英文跟我解釋因果、
輪迴這些事情，這都還不稀奇。
有趣的事情在後頭呢！
師父一聽完我跟他提到的個人煩惱的時候，
他索性要我左手提起他剛買的三罐番茄汁，
一邊提著，一邊跟他說話。
可想而知，我左手感覺到疲勞的程度，
跟時間成了正比。
也懊惱著為何師父要我一邊提著三罐蕃茄汁，
一邊跟他說話。
受不了這樣的酸楚，我自行把左手放下，
卻聽到師父跟我說：
「 Hold it up, and keep talking to me.」
聽到這樣的話，心理不免起了疑心，
我手提的那麼酸，為何不讓我放下手上的重物，
輕鬆地與他對談？
約莫過了15分鐘，我的左手實在承受不住了，
才聽見師父跟我說：
「 Now you can put it down.」。
看著我狐疑的臉，師父居然笑了出來。
「你不喜歡提著重物跟我說話，
為何你卻喜歡帶著煩惱來跟我 說話，過著你的生活呢？
手酸了，放下就好，對待煩惱，不也是這樣？
或是這些煩惱就像是那些番茄汁一樣，
是你自己用手把它們給舉起來的呢？」
有趣的經驗，對吧？
最近我開始這樣的練習，
一手舉起有重量的東西，一邊想著事情。
手酸了，自然會放下手上的東西，
看看有一天，我會不會也學到，
心累了，就把心事給放下來。
我們能很容易的放下有形的重物，
卻很難放下無形的重擔。
執著的人生會讓自己承擔莫需有的重擔。
所以學習放下執著也就在學習人生自在。
特別是他叫我舉起蕃茄汁跟他說話 的經驗。
我們約在新竹的一家茶館用英文談論著心經，
師父用英文跟我解釋因果、
輪迴這些事情，這都還不稀奇。
有趣的事情在後頭呢！
師父一聽完我跟他提到的個人煩惱的時候，
他索性要我左手提起他剛買的三罐番茄汁，
一邊提著，一邊跟他說話。
可想而知，我左手感覺到疲勞的程度，
跟時間成了正比。
也懊惱著為何師父要我一邊提著三罐蕃茄汁，
一邊跟他說話。
受不了這樣的酸楚，我自行把左手放下，
卻聽到師父跟我說：
「 Hold it up, and keep talking to me.」
聽到這樣的話，心理不免起了疑心，
我手提的那麼酸，為何不讓我放下手上的重物，
輕鬆地與他對談？
約莫過了15分鐘，我的左手實在承受不住了，
才聽見師父跟我說：
「 Now you can put it down.」。
看著我狐疑的臉，師父居然笑了出來。
「你不喜歡提著重物跟我說話，
為何你卻喜歡帶著煩惱來跟我 說話，過著你的生活呢？
手酸了，放下就好，對待煩惱，不也是這樣？
或是這些煩惱就像是那些番茄汁一樣，
是你自己用手把它們給舉起來的呢？」
有趣的經驗，對吧？
最近我開始這樣的練習，
一手舉起有重量的東西，一邊想著事情。
手酸了，自然會放下手上的東西，
看看有一天，我會不會也學到，
心累了，就把心事給放下來。
我們能很容易的放下有形的重物，
卻很難放下無形的重擔。
執著的人生會讓自己承擔莫需有的重擔。
所以學習放下執著也就在學習人生自在。
Tuesday, December 11, 2007
Big problem with simple solution
Difference between Focusing on Problems and Focusing on Solutions
Case 1
When NASA began the launch of astronauts into space, they found out that
the pens wouldn't work at zero gravity (ink won't flow down to the writing
surface). To solve this problem, it took them one decade and $12 million.
They developed a pen that worked at zero gravity, upside down, underwater,
in practically any surface including crystal and in a temperature range
from below freezing to over 300 degrees C.
And what did the Russians do...?? They used a pencil.
Case 2
One of the most memorable case studies on Japanese management was the case of the empty soapbox, which happened in one of Japan 's biggest cosmetics companies. The company received a complaint that a consumer had bought a soapbox that was empty. Immediately the authorities isolated the problem to the assembly line, which transported all the packaged boxes of soap to the delivery department. For some reason, one soapbox went through the assembly line empty. Management asked its engineers to solve the problem.
The engineers worked hard to devise an X-ray machine with high-resolution
monitors manned by two people to watch all the soapboxes that passed
through the line to make sure they were not empty. No doubt, they worked
hard and they worked fast but they spent a huge amount to do so.
But when a rank-and-file employee in a small company was posed with the
same problem, he did not get into complications of X-rays, etc., but
instead came out with another solution. He bought a strong industrial
electric fan and pointed it at the assembly line. He switched the fan on,
and as each soapbox passed the fan, it simply blew the empty boxes out of
the line.
Moral Of The Story:
Always look for simple solutions. Focus on solutions not on problems.
Case 1
When NASA began the launch of astronauts into space, they found out that
the pens wouldn't work at zero gravity (ink won't flow down to the writing
surface). To solve this problem, it took them one decade and $12 million.
They developed a pen that worked at zero gravity, upside down, underwater,
in practically any surface including crystal and in a temperature range
from below freezing to over 300 degrees C.
And what did the Russians do...?? They used a pencil.
Case 2
One of the most memorable case studies on Japanese management was the case of the empty soapbox, which happened in one of Japan 's biggest cosmetics companies. The company received a complaint that a consumer had bought a soapbox that was empty. Immediately the authorities isolated the problem to the assembly line, which transported all the packaged boxes of soap to the delivery department. For some reason, one soapbox went through the assembly line empty. Management asked its engineers to solve the problem.
The engineers worked hard to devise an X-ray machine with high-resolution
monitors manned by two people to watch all the soapboxes that passed
through the line to make sure they were not empty. No doubt, they worked
hard and they worked fast but they spent a huge amount to do so.
But when a rank-and-file employee in a small company was posed with the
same problem, he did not get into complications of X-rays, etc., but
instead came out with another solution. He bought a strong industrial
electric fan and pointed it at the assembly line. He switched the fan on,
and as each soapbox passed the fan, it simply blew the empty boxes out of
the line.
Moral Of The Story:
Always look for simple solutions. Focus on solutions not on problems.
Saturday, December 08, 2007
赛果尘埃落定
Rank, User, Holdings
1, tiger chan, RM1,107,600.74
2, big girl, RM1,032,293.90
3, dixonng33, RM990,666.50
前三名都是华裔，两男一女。
凭250K在两个月的时间里，大约翻了三倍。赞！:)
1, tiger chan, RM1,107,600.74
2, big girl, RM1,032,293.90
3, dixonng33, RM990,666.50
前三名都是华裔，两男一女。
凭250K在两个月的时间里，大约翻了三倍。赞！:)
Friday, December 07, 2007
两个启示
修理手表
原以为只是电池够钟了，结果钟表店的老板说是电板坏了。
十天内修好，大约RM180-200，六个月保证期。
既然要修，决定亲自把它送回原厂，维修中心就在我工作的附近。
结果维修员十分钟左右就让它继续跳动，还一文不收。
用了三年多，已过了十二个月的保证期，现在竟然一文不收，太感动了！
据说只是电池问题。-_-"
保单断保
每年保费到期后还有三十天缓冲期，如果要断保就要等到期后，
可以多拿点现金红利。:)
原以为只是电池够钟了，结果钟表店的老板说是电板坏了。
十天内修好，大约RM180-200，六个月保证期。
既然要修，决定亲自把它送回原厂，维修中心就在我工作的附近。
结果维修员十分钟左右就让它继续跳动，还一文不收。
用了三年多，已过了十二个月的保证期，现在竟然一文不收，太感动了！
据说只是电池问题。-_-"
保单断保
每年保费到期后还有三十天缓冲期，如果要断保就要等到期后，
可以多拿点现金红利。:)
Thursday, December 06, 2007
一百个大学生就有99个回答错误的小学算术题
这是网上声称 [一百个大学生就有99个回答错误的小学算术题]：-
有个顾客到王老板的店里买了件礼物，这礼物成本是18元，标价21元。这顾客掏出一百元付钱，王老板当时没零钱，就用那一百元向街坊换了一百元零钱，找给那顾客79 元。但街坊后来发现那一百元是假钞，王老板无奈还了街坊一百元。 * 请问： 王老板在这次交易中到底损失了多少钱？
（嘿~！别小看这小小的问题，这可能会考倒你喔！）
答案：RM97
解说：王老板用RM18买了件礼物，卖出去RM21，所以他在交易中赚了RM3。 顾客付RM100给王老板（记得这RM100是属于顾客的），王老板和街坊换了100块的零钱（记得这RM100还是属于顾客的，街坊只是用顾客的钱换成零钱而已），然后找了RM79给顾客（RM100-RM21= RM79）。所以，算呀算！ 他还是赚RM3（RM21-RM18=RM3）。 但是，后来街坊发现那RM100是假钞（记得这RM100还是属于顾客的，街坊只是用顾客的钱换成零钱而已），所以王老板用自己的RM100还回给街坊，所以他损失了RM100。 从损失的RM100 - RM3的盈利，他总共损失了RM97。
有个顾客到王老板的店里买了件礼物，这礼物成本是18元，标价21元。这顾客掏出一百元付钱，王老板当时没零钱，就用那一百元向街坊换了一百元零钱，找给那顾客79 元。但街坊后来发现那一百元是假钞，王老板无奈还了街坊一百元。 * 请问： 王老板在这次交易中到底损失了多少钱？
（嘿~！别小看这小小的问题，这可能会考倒你喔！）
答案：RM97
解说：王老板用RM18买了件礼物，卖出去RM21，所以他在交易中赚了RM3。 顾客付RM100给王老板（记得这RM100是属于顾客的），王老板和街坊换了100块的零钱（记得这RM100还是属于顾客的，街坊只是用顾客的钱换成零钱而已），然后找了RM79给顾客（RM100-RM21= RM79）。所以，算呀算！ 他还是赚RM3（RM21-RM18=RM3）。 但是，后来街坊发现那RM100是假钞（记得这RM100还是属于顾客的，街坊只是用顾客的钱换成零钱而已），所以王老板用自己的RM100还回给街坊，所以他损失了RM100。 从损失的RM100 - RM3的盈利，他总共损失了RM97。
Tuesday, December 04, 2007
Sunday, December 02, 2007
Subscribe to:
Posts (Atom)