活着: work

Classical learning curves for some common editors

Fri, 03 Mar 2006 09:46:53 GMT

Disclaimer: I don't agree with the Visual Studio one, though.

anti-turing

Wed, 18 Jan 2006 07:56:38 GMT

The newbie realizes that the difference between code and data is trivial.

The expert realizes that all code is data.

And the true master realizes that all data is code

insane

Mon, 01 Aug 2005 06:48:47 GMT

i have one vs project, when visual studio 2005 opens it, it takes 1G VM. and i take a cup of coffee before it closed.

f*cking insane visual studio.

继续打

Fri, 15 Jul 2005 17:18:58 GMT

紧赶慢赶，今天算是完成了计划的TEST CODE COMPLETE/FULL PASS。基本上，因为DESIGN拖后了很多，DEV和TEST的SCHEDULE都压缩了不少；不过最后确都按时完成了。

从阳的方面说，一切都可以定量。一个项目有多少个FEATURE POINT，每个按COMPLEXITY打分加总，以CORP. LEVEL/DEPT. LEVEL的METRICS DATABASE为根据计算工作量再考虑RESOURCE LEVEL包括HEAD COUNT和MATURITY就能作出可信的计划。

从阴的方面说，这一切是数字游戏。“事实是坚硬的，所以要把它变成数字”（忘记谁说的了，GOOGLE也没找到）。所谓SCHEDULE这个东西就像面团，揉揉搓搓，可拉可挤。只要设定DEADLINE和KICK OFF POINT，总能做出个像样的PLAN来。而且计划赶不上变化，所谓PLAN/SCHEDULE/REPORT，不过是老板获得虚幻的安全感的来源而已。而按照墨菲定则，你有多少时间和人力就会有多少事情要做。

AGAIN，所谓事实，就在两点之间的某个地方吧。

作为中国人，这个就是阴阳调和。

作为双子座，这个就是见老板说老板话，见朋友说朋友的话。

而作为人，这个就叫做DOUBLE THINK。

下午新员工指南

Mon, 30 May 2005 09:59:18 GMT

遇一HR大尾巴狼，张口KAIFU闭口HONGJIANG，无语。。。

i love this company

Fri, 13 May 2005 10:18:14 GMT

刚才在楼面里走了一圈，发现有人在扔篮球，居然还有一桌在打麻将。

OMG, I LOVE THIS COMPANY!

如果再来桌大怪就完美了。。。

总有一些对话让你感动

Wed, 11 May 2005 01:48:53 GMT

Nathan: Steve, you know how ++ will increment, right?
Steve: Right ....
Nathan: Okay, so how do you increment by 11?

第一天上班

Mon, 11 Apr 2005 06:16:25 GMT

第一天，报道，安排位子，整理PC，吃饭。这里上网可真快，哈哈。

按照这个标准,我们公司的代码90%不合格,我写的代码最多50%合格

Fri, 18 Feb 2005 06:39:13 GMT

If your function is more than 10 lines long, you should start to consider splitting it.

如果你的函数超过10行，你应该开始考虑分隔它。

If it's more than 100 lines long, you're probably doing something wrong.

如果它超过100行，你的做法可能不对。

If a chunk of code can't fit on one page (two, max) it's too damn long. You're trying to do too much in one spot, and the goonies and golems will bit you in the ass.

如果一段代码不能显示在一页（最多两页）之内，它太长了。。。

If it needs more comments than code, it's a sign its overly-complicated and you need to rethink what you're doing and how you're doing it. In other words, your algorithm sux the bag.

如果你需要的注释比代码还多的话，这是你的代码过分复杂的标志，你需要重新想想你在做什么和你是怎么做的。就是说你的算法有问题。

If you can't write test cases for it because it's too tightly coupled to the rest of your code, you probably misunderstood the problem in the first place (or at least you're approaching it from the wrong direction)...

如果你不能写一些测试用例来测试它因为它和你别的部分的代码捆绑太紧密，那么你可能一开始对问题的理解就有问题（或者你的解决方法不对）。

All the comments and documentation in the world won't make spaghetti understandable or maintainable.

世界上所有的注释和文档加在一起都不能让面条代码变的容易理解和维护。

spaghetti：面条代码，意思是看起来想面条一样乱糟糟的代码。