醉生梦死

三月烂桃花开

2009-03-28T08:06:00.001+08:00

交大校园里开了好多

-- 发送自我的 iPhone

苹果汽水

2009-03-21T12:19:00.001+08:00

上初中最惬意的事情莫过于中午踢完足球到小卖部买一杯苹果汽水

-- 发送自我的 iPhone

试试看

2009-02-15T10:29:00.000+08:00

第一次用blogpress发

-- 发送自我的 iPhone

douban

2008-11-03T18:22:00.001+08:00

doubanclaimfdc50ea0ff525e24

2008-10-09 21:59:34

2008-10-30T15:00:00.040+08:00

农历九月十一，壬午大利正南，忌驾马，宜造车

最近三四个月，除了星期五，基本没有在11点之前下过搬

我是不是疯子？

]]>

written at 2008-10-09 21:59:34

2008-10-15 08:18:21

2008-10-30T15:00:00.039+08:00

农历九月十七，戊子大利东南，忌移徒，宜教牛马

我又要为前途担忧了，同事告诉我老大有可能要走，不知道他走了以后公司还顶不顶的住

想当初他的存在是我来这里的最主要原因，毕竟大牛不是很好找阿

一下子对公司的前途和自己的前途都有点怀疑，公司剩下的人里，真正的技术牛人也不多了，现在的leader是非科班出身，感觉对管理并不在行，老板对技术细节关心也比较少。而且从前老大也是比较经常为我们谋利的，几次向老板提出给我加薪。

我其实一点不想很短的时间里再还个工作，之前我考虑至少在这里干到拿了工程硕士学位之后再考虑别的，看来果然不能计划这么遥远的事情，什么都会变的

]]>

written at 2008-10-15 08:18:21

2008-10-03 13:58:06

2008-10-30T15:00:00.037+08:00

未时日过中天，骄未散

今天又跑过来加班，就来了很没劲的几个人，连续几天不断的噩梦。

前天梦见被蛇咬，昨天又梦见杀了很多人，不停的逃跑

休息了几天也没干什么事情，昨天晚上想叫人出来吃饭转了半天号码簿也没发现个合适的

女人们似乎不适合没有理由的1v1吃饭，男人们要么忙要么干脆不理

大学毕业之后看上去那种能随便一起吃饭喝酒的人越来越少

啸宇兄回上海之后有了个女朋友，当然跟以前不是一个德行

北去日本之后在上海找了个从未谋面的女朋友，很奇妙的一件事

好多年前论坛里那个写淡淡的忧伤的文字的比我小一岁的小姑娘嫁了人而且生了孩子

潜水艇跟处了好多年的男朋友‘暂分’ 前些日子见她，感觉略微成熟了些

去过阿毛的寝室，跟从前无甚变化

倒是阿强忽然对工作变得aggressive起来，他们小两口幸福甜蜜，只是从那之后寝室之间不像从前亲密无间了

只有我，天天颠沛流离在贫穷于欲望之间

男人与男人之间是不是不应该有什么，男人和女人之间也不应该有什么

那我还有什么

我知道我还有牛逼的梦想，只是有时觉得彷徨

]]>

written at 2008-10-03 13:58:06

2008-09-28 22:13:42

2008-10-30T15:00:00.035+08:00

亥时人定归本，早安眠

昨天折腾了下python3.0,语法都变了好多，没有了print这样的语法糖，变成了函数，变量名可以是utf8的

很多东西都规范了一些，所以所有的python相关的东西全部不能正常使用了

平常经常用的python-memcached, python-mysqldb, python-django等等等等都无法使用

估计半年内还是用python2.5了。

上周花了半天时间把我的项目平稳过渡到django1.0 。参照了几个open source的东西再看看我们自己的

很多地方都写的很猥琐，最主要是form使用django自己的form就会让后台和前台都非常的优雅

目前几个项目用的界面都不是很复杂，规模上去一点的话几十个模板夹杂css, js, html 惨不忍睹

发现很早就把花生壳弄到路由器里了，这样我机器上跑的网站在外面也可以访问到

然后就不知道做什么好了

bus很方便被订阅到各种客户端或rss输出的地方

还是趁着这时候多练练数据结构

刚装了个gentoo唯一不爽的就是包管理通过portage，速度慢的惨绝人寰

]]>

written at 2008-09-28 22:13:42

2008-09-27 21:58:58

2008-10-30T15:00:00.033+08:00

农历八月廿八，庚午大利西北，忌作灶，宜裁衣

好多年好多年以后我会老会死会忘记你们所有人

我知道你也会

我喜欢有好听的音乐的电影

可是生活没有伴奏

它也会很精彩

]]>

written at 2008-09-27 21:58:58

2008-09-22 21:41:17

2008-10-30T15:00:00.031+08:00

9.22

今天报好名，又花了320块算算还有两个月时间交大老师说你不报我们的辅导班自己复习就要抓紧了

想了想两个月有多长回退两个月我已经在徐家汇了原来张江已经好远

我哥叫我寄点钱给我妈，我倒是想但真的一点钱都没有阿

有时候真觉得环境挺资本主义的老板也挺能压榨

但是我在这里能不断的学习半年时间已经脱胎换骨这是我留在这里的理由

]]>

written at 2008-09-22 21:41:17

2008-08-09 20:57:54

2008-10-30T15:00:00.029+08:00

8.09
又碰到这人

2008-08-09 20:56:46

2008-10-30T15:00:00.027+08:00

8.09

还是很想念张江、

想念公司规模还很小的时候几个人的其乐融融
想念夜里一个人骑车半个小时空无一人的放纵
想念上班路上抬首瞥见头顶呼啸而去的磁悬浮
想念集电港垂柳小道和余辉里抛向天空的鱼钩
想念去地铁路上就能看见的地平线和半个落日

]]>

written at 2008-08-09 20:56:46

2008-08-04 20:55:55

2008-10-30T15:00:00.025+08:00

8.04
和大学同学吃了顿饭

2008-07-29 20:53:55

2008-10-30T15:00:00.023+08:00

7.30

2008-07-26 10:58:03

2008-10-30T15:00:00.021+08:00

挪窝

又想挪窝了

每次都要爬上来写很烦

Bus又不开放API

要找个有客户端的，饭否那样又太白菜

]]>

written at 2008-07-26 10:58:03

2008-07-26 10:49:02

2008-10-30T15:00:00.019+08:00

0726

前天晚上之后果然感觉到那个深深的失落感

白天突然想起“幸福”一词，下颚突然猛的抽了一下，不知道是不是身体较之大脑对这个词汇更加陌生了

然后努力回忆之前，正巧阿强这时候QQ我说下周请我和阿毛吃饭，我才舒展过来

只有面对你们我才是真的我

工作，学习已经让我很久很久丢掉了回忆的习惯

每周五下班要路过一次港汇，来刺激自己

要有钱

可是前不久做了个梦，我拼搏十数年，公司上市了，我成了富翁

再去学校泡小姑娘，想找回当年的纯真，我撒下大巴钞票

姑娘冷冷的告诉我，我要的不是你的钱

偶尔迷失不知自己想什么只能说服自己还有更多的事情要做

独立担负一个产品很多东西要改进缺人手有新人的话还要带

但是失眠的时候很多很多总想这个世界很扯

找人一起毁灭地球但志同道合的人也不多

地球也很强大

]]>

written at 2008-07-26 10:49:02

2008-07-20 15:02:16

2008-10-30T15:00:00.017+08:00

一梦

梦到我在一个类似FF8那样的学校里上学，无比华丽的电梯

曾经我也是个爱幻想的人，如今为何这般无趣

总想要离开，却不知道哪里才能换骨脱胎。。。

]]>

written at 2008-07-20 15:02:16

2008-07-15 08:33:27

2008-10-30T15:00:00.015+08:00

又是他
今天去游泳，游到一半看到一个熟悉的面孔，本能的立刻逃跑，不过还是没有逃过
丫游到我面前，台词跟几年前一模一样“自由泳游的不错啊”，然后自我介绍，问我是不是住这附近
我操，其实听到他的声音我就认出来了，他竟然一点没认出我。然后就跟我要联系方式，我想了想说我扣扣不怎么用，然后告诉了他一个我最长的MSN，他说他要上去了，我说我还要一会
结

2008-07-02 22:19:33

2008-10-30T15:00:00.013+08:00

正式上班一年来
跳了一次槽
恋了一次爱
新认识了不少人
各行各业
原则是一年学习一门新语言
从hello world开始学习了几种语言
c, python, javascript, unix shell, 好吧cache`也算一门

from cover to cover：
The Definitive Guide to Django
程序员修炼之道(从小工到专家) / The Pragmatic Programmer
Dive Into Python
Python 2.1宝典 / Python 2.1 Bible
征服Python--语言基础与典型应用
正则表达式必知必会
.NET框架程序设计（修订版）——微软.NET程序员系列
c++ primer

没有统计写过的程序的行数的习惯，估计不算多
在学校的最后一年我最怀念的地方是同济大学

大学里的朋友出国的出国，各分东西的工作，还有好多都不知去向了
上班这一年里我最怀念的地方是张江的所有地方
张江多半地方都看得到日出日落和地平线，我却能找到独上高楼的感觉
很怀念

徐家汇很繁华，但我熟悉的仅仅是公司到寝室十分钟脚程小路
没有多少灯红酒绿，
菜场，打牌的老头们，垃圾车的鸣笛

-----------------
之后一年准备考交大的MSE
很尴尬的圆梦之旅
5年前高考填志愿被说服不报考交大是我最后一次在人面前哭
如今。。。]]>

written at 2008-07-02 22:19:33

2008-06-28 13:01:01

2008-10-30T15:00:00.011+08:00

sss
doubanclaim5f314d2421ceb614]]>

written at 2008-06-28 13:01:01

2008-06-28 09:56:00

2008-10-30T15:00:00.009+08:00

那时你拖我手
独自享受黑夜总忍住告诉你只有你在的夜我才不会失眠
问我是否真心时候认真又慌乱的眼神我久久难忘

有些话总是说起来简单做起来很难]]>

written at 2008-06-28 09:56:00

2008-06-28 09:54:45

2008-10-30T15:00:00.007+08:00

告别
去张江收拾了东西，很迅速
所有的东西拖了一车
这个荒凉的自由的热土我魂牵梦绕的那个地方
我就要与他告别了
带不走新开的那家水果卖场，和我讨厌而怀念的鸡公煲
无人的盛夏路在这里随意荡漾是最舒服的
祖冲之路高斯路张衡路毕升路李时珍路郭守敬路蔡伦路
一个个名字让人永远记得
芳春路，盛夏路，金秋路，银冬路
可惜不能走完每条
还有集电港新加坡式的格局，可以钓鱼的小河
一样带不走的还有LL，我给不了她任何东西
如此如此]]>

written at 2008-06-28 09:54:45

2008-06-26 09:55:28

2008-10-30T15:00:00.005+08:00

工作操蛋生活操蛋
广东那边通知来说老子担当的这个项目规模减半
大概项目预算要减半了，进公司以来比较大的一个滑铁卢。
因为这个到后期基本是我一个人在做，所以责任应该都在我
拖了不少时间，先是上海测试的时候比较偷懒，没有坚持顶着
再是公司搬家的时间，不小心把服务器的ssh杀掉了导致几天不能工作
中间一些整体上的布局也没有考虑好
最后独立加的统计模块工作方式太冒险，都是直接在服务器上改代码
既没有版本管理也没有按照比较正式的方法写，都在乱来
希望安稳的进行部署实施

交大的软工硕士11月就要考试，还有几个月复习
绝对不允许失败
我要让自己相信我自己的执行力
引用一句
我不是要证明我了不起，我是要别人知道，我失去的东西我一定要亲手拿回来。]]>

written at 2008-06-26 09:55:28

2008-06-22 09:54:59

2008-10-30T15:00:00.003+08:00

八万行
开始读nginx的代码
昨天看到俄罗斯痛快的把荷兰踢回家，群里有人说毛子的实力
说到软件上面，毛子的软件真厉害，卡巴斯基和巴基斯坦虽然只有基巴关系
我现在读的nginx代码可够我喝一壶了
八万行C代码，说实话C语言我还真没写过一行
NNDX]]>

written at 2008-06-22 09:54:59

2008-06-12 09:54:14

2008-10-30T15:00:00.001+08:00

骑车到集电港转了转
心情无比舒畅
集电港现在成了我心中完美的工作生活地点
附近公司略看了看，有AMD,51JOBS]]>

written at 2008-06-12 09:54:14

2008-06-06 09:53:17

2008-10-30T14:59:00.003+08:00

欧锦赛记忆
2004年，三个煞笔男和几个妞在学校酒吧联谊，我弄了弄大一暑假布置的程序题，坐了一会回去熬夜看荷兰对捷克，看到2：0的时候睡着，第二天看到新闻才

2008-05-26 10:03:34

2008-10-30T14:59:00.001+08:00

测试程序

奥运会

NBA

贝克汉姆

]]>

written at 2008-05-26 10:03:34

2008-05-26 10:03:34

2008-10-29T08:27:00.001+08:00

测试程序

奥运会

NBA

贝克汉姆

]]>

written at 2008-05-26 10:03:34

2008-05-13 15:59:27

2008-10-29T08:26:00.003+08:00

5.13

地震了就。。。我还有在重庆的同学亲戚，现在电话打不进，连咯不上

5.12 释迦摩尼佛的诞辰日

佛说五百年正法，后五百年像法，再一万年末法。所有的佛都闭上了眼睛，蒙住了耳朵，任由众生自生自灭

阿弥佗佛

我感到很惭愧，一边我一直在说自己信佛，一边又在不断产生非善念，不守戒

我很矛盾

希望一灯入暗室这五个字不要成为我给自己的台阶

]]>

written at 2008-05-13 15:59:27

2008-05-11 18:09:29

2008-10-29T08:26:00.001+08:00

5.10

还有大约半个月公司要搬到徐家汇去了，开销又要大了，不过只要我能撑的下去，我是不会愿意住家里的。

希望24号能顺利去看，最贵的票200块钱。。好便宜

加油加油，我来了

]]>

written at 2008-05-11 18:09:29

2008-03-06 15:03:18

2008-10-29T08:25:00.057+08:00

--平衡二叉树

这个恐怕是整个《数据结构》教科书里面最难的和最“没用”的数据结构了（现在的教科书还有部分算法内容）。说它没用，恰恰是因为它太有用——有着和普通的二叉搜索树完全一样的接口界面，绝大多数情况下比普通的二叉搜索树效率高（很多）。因此，通常情况下，人们都是一劳永逸的——写完后就重用，而不会再写了。所以说，你虽然学完了平衡二叉树，但很可能你永远也不会亲自写一个。你现在随便在身边拉个人，让他来写一个，能顺利的写出来的恐怕不多，玩笑之词，且勿当真。

在开始写之前，我很担心，能不能把这部分写清楚，毕竟书上满天的switch…case，并且还只是一半——有左旋没有右旋，有插入没有删除。后来，我变得有信心了——因为书上都没有说清楚，都在那里说梦话。我没有找到AVL树的发明者的原著（G. M. Adelson-Velskii and Y. M. Landis. An algorithm for the organization of information. Soviet Math. Dokl., 3:1259--1262, 1962.）也不知道我下面所写的是不是体现了发明者的本意，但至少，我认为现在的教科书歪曲了发明者的本意。

基本概念

Ø 平衡下面的引文出自Algorithms and Data Structures （Niklaus Wirth, Prentice-Hall, Englewood Cliffs, NJ, 1986 ISBN: 0-13-022005-1 pp. 215 – 226）

One such definition of balance has been postulated by Adelson-Velskii and Landis [4-1]. The balance criterion is the following:

A tree is balanced if and only if for every node the heights of its two subtrees differ by at most 1. Trees satisfying this condition are often called AVL-trees (after their inventors). We shall simply call them balanced trees because this balance criterion appears a most suitable one. (Note that all perfectly balanced trees are also AVL-balanced.) The definition is not only simple, but it also leads to a manageable rebalancing procedure and an average search path length practically identical to that of tbe perfectly balanced tree.

科技文都比较好懂，本人翻译水平比较差，就不献丑了，我只想让大家注意最后一段的画线部分，平衡化应该是易于操作的，而绝不是现在你在书上看到的铺天盖地的switch…case。

Ø 旋转

平衡化靠的是旋转。参与旋转的是3个节点（其中一个可能是外部节点NULL），旋转就是把这3个节点转个位置。注意的是，左旋的时候p->right一定不为空，右旋的时候p->left一定不为空，这是显而易见的。

p				p
p		左旋		t
	t		(p)
（NULL）				（NULL）

可以看到，左旋确实是在向“左”旋转，还是很形象的。右旋是左旋的镜像，就不再另行说明了。下表是左旋和右旋各个节点的指针变换情况。（括号表示NULL的情况不执行）

左旋		右旋
t->parent = p->parent	p->parent = t	t->parent = p->parent	p->parent = t
(t->left->parent = p)	p->right = t->left	(t->right->parent = p)	p->left = t->right
t->left = p	p = t	t->right = p	p = t

Ø 平衡因子（bf——balance factor）

AVL树的平衡化靠旋转，而是否需要平衡化，取决于树中是否出现了不平衡。为了避免每次判断平衡时，都求一下左右子树的高度，引入了平衡因子。很可能是1962年的时候AV&L没有亲自给出定义，时下里平衡因子的定义乱七八糟——我看了4本书，两本是bf ＝左高－右高，两本是bf ＝右高－左高。最有意思的是两本中国人（严蔚敏和殷人昆）写的一本左减右，一本右减左；两本外国人写的也是这样。虽然没什么原则上的差别，可苦了中国的莘莘学子们——考试的时候可不管你是哪个门派的。我照顾自己的习惯，下面的bf = 左高－右高，习惯不同的请自己注意。

这样一来，是否需要平衡化的条件就很明了了——| bf | > 1。如果从空树开始建立，并时刻保持平衡，那么不平衡只会发生在插入删除操作上，而不平衡的标志就是出现bf == 2或者 bf == -2的节点。

插入和删除

在AVL树插入和删除，实际上就是先按照普通二叉搜索树插入和删除，然后再平衡化。可以肯定的说，插入和删除需要的最多平衡化次数不同（下面会给出根本原因），但这不表明插入和删除时的平衡化的思路有很大差别。现有的教科书，仅仅从表面上看到了到了平衡化操作次数不同的假象，而没有从根本上认识到插入和删除对称的本质，搞得乱七八糟不说（铺天盖地的switch…case），还严重的误导了读者——以为删除操作复杂的不可捉摸。

AVL树体现了一种平衡的美感，两种旋转是互为镜像的，插入删除是互为镜像的操作，没理由会有那么大的差别。实际上，平衡化可以统一的这样来操作：

1． while (current != NULL)修改current的平衡因子。

Ø 插入节点时current->bf += (current->data > *p)?1:-1;

Ø 删除节点时current->bf -= (current->data > *p)?1:-1;

Ø current指向插入节点或者实际删除节点的父节点，这是普通二叉搜索树的插入和删除操作带来的结果。*p初始值是插入节点或者实际删除节点的data。因为删除操作可能实际删除的不是data。

2．判断是否需要平衡化

if (current->bf == -2) L_Balance(c_root); else if (current->bf == 2) R_Balance(c_root);

3．是否要继续向上修改父节点的平衡因子

Ø 插入节点时if (!current->bf) break;这时，以current为根的子树的高度和插入前的高度相同。

Ø 删除节点时if (current->bf) break;这时，以current为根的子树的高度和删除前的高度相同

Ø 之所以删除操作需要的平衡化次数多，就是因为平衡化不会增加子树的高度，但是可能会减少子树的高度，在有有可能使树增高的插入操作中，一次平衡化能抵消掉增高；在有可能使树减低的删除操作中，平衡化可能会带来祖先节点的不平衡。

4．当前节点移动到父节点，转1

p = &(current->data); current = current->parent;

完整的插入删除函数如下：

bool insert(const T &data)

{

if (!BSTree<T>::insert(data)) return false; const T* p = &data;

while (current)

{

current->bf += (current->data > *p)?1:-1;

if (current->bf == -2) L_Balance(c_root);

else if (current->bf == 2) R_Balance(c_root);

if (!current->bf) break;

p = &(current->data); current = current->parent;

}

return true;

}

bool remove(const T &data)

{

if (!BSTree<T>::remove(data)) return false; const T* p = &r_r_data;

//在class BSTree里添加proteceted: T r_r_data，在BSTree<T>::remove(const T &data)里修改为实际删除的节点的data

while (current)

{

current->bf -= (current->data > *p)?1:-1;

if (current->bf == -2) L_Balance(c_root);

else if (current->bf == 2) R_Balance(c_root);

if (current->bf) break;

p = &(current->data); current = current->parent;

}

return true;

}

你可以看到，他们是多么的对称

显然的，平衡化后的子树应该是平衡的，以此为原则，很容易得知在各种情况下应该怎么旋转。

private:

void L_Balance(BTNode<T>* &p)

{

if (p->right->bf == 1) R_Rotate(p->right);

L_Rotate(p); current = p;

}

void R_Balance(BTNode<T>* &p)

{

if (p->left->bf == -1) L_Rotate(p->left);

R_Rotate(p); current = p;

}

他们也是对称的。

修改平衡因子

这是整个AVL树能运转的核心，现在的教科书，也正是因为没有真正弄明白如何修改平衡因子，才搞的switch…case满天飞。平衡因子的变化发生在旋转中——正因为这样，旋转才能有平衡化的作用——所以，应该把修改平衡因子的工作放在旋转操作中，而不是放在平衡化中。让我们来看看可能的旋转会带来的平衡因子变化的情况：

左旋（旋转后p暂时没有没有改变）				右旋（旋转后p暂时没有没有改变）
旋转前p	旋转前t	旋转后p	旋转后t	旋转前p	旋转前t	旋转后p	旋转后t
－2	0	－1	1	2	0	1	－1
－2	－1	0	0	2	1	0	0
－2	－2	1	0	2	2	－1	0
－1	0	0	1	1	0	0	－1
－1	－1	1	1	1	1	－1	－1
－1	1	0	2	1	－1	0	－2

旋转的最初发生是因为bf==2或bf==－2，对bf==1或者bf==-1的旋转是为了平衡化的需要——平衡化时的旋转p和t的bf不能异号。表面看起来这张表很凌乱，似乎没什么规律，其实不然。

对于左旋——p的右子树从t变成了t的左子树，显然p的右子树高度至少减1。t的bf代表了原来的t左右子树的高度差，如果t->bf<0，则p的右子树的高度还要减少|t->bf|。t的左子树在原来的左子树上面又多了一个p，显然左子树高度至少加1。在p的平衡因子修改完之后，如果p->bf>0那么t的左子树高度还要增加p->bf。

综合起来就是++(p->bf) -= t->bf < 0?t->bf:0; ++(t->bf) += p->bf > 0?p->bf:0;

对于右旋同理。--(p->bf) -= t->bf > 0?t->bf:0; --(t->bf) += p->bf < 0?p->bf:0;

可以看到这也是对称的。

完整的AVL树实现

#define c_p current->parent

#define c_root (c_p?((c_p->left == current)?c_p->left:c_p->right):root)

written at 2008-03-06 15:03:18

2008-02-27 21:50:54

2008-10-29T08:25:00.056+08:00

2.27

休息的日子差不多了，明天晚上去雁荡山，之后就要开始新工作了。图书馆借来了两本书，一本python的一本JS的，准备开始新生活，也许三个月没有网，在这两三年里要好好磨练磨练，变得更强大。我这才想明白，原来谈恋爱的时候，觉得她生命力不能没有激情不能平淡如水的日子觉得我恰恰相反。其实我们都一样渴望新鲜，这一年来，越来越多的曾经的坚持被我检验为不值一提的玩笑。我的信仰我的梦想我的人生，我都不知道是不是真的。我已经在什么是对的什么是错的的道路上走得太远，我现在相信，无论何时何地何种情况，都要对自己诚实。同时我也拒绝变得更所谓的成熟，昨天看了一部电影，一直以来很想看的，《归乡》。看完有种很难受的感情，压抑着不能宣泄，我想到为什么小孩子能够成长能够变化，因为他的心不够成熟，在见到新鲜东西的时候不会立刻反应出以往的已经形成的经验。所以他们会变化，成年人有了经验，变得世故，结果把很多好东西都拒绝了。

今天有个MM问我为什么不找女朋友，我扯了几句，这段时间也想过这个问题，但是我自己也不确定，到底是因为没有条件导致没有兴趣还是因为没有兴趣借口没有条件，管他呢反正都是一个答案

]]>

written at 2008-02-27 21:50:54

2007-12-13 21:27:48

2008-10-29T08:25:00.055+08:00

12.13

既然傻逼了，就傻逼到底吧

这是我昨天看《这个男人来自地球》的第一感受。看这片的动机主要来自好奇，看之前也了解了一些内容。片子形式是从头到尾的谈话，涉及的面很多，生物学，地理，社会，宗教，然而他是以一种荒谬的形式来叙述：这男人活了14000年。其实从头到尾就是几个人类在探讨人类自己，话题很多很杂而导演把它统统放进这么一个姑且叫他电影的空间里面。想起一句话，人类一思考，上帝就发笑。但这个男人说自己就是上帝。不知道导演对于上帝的看法是什么，估计应该没有所谓的敬畏吧

看完我想到最多的是，这片的定位在哪里？首先我把像塔可夫斯基的电影称作“电影”这当然曲高和寡，另一端是像魔戒，黑客帝国等商品电影消费电影，而这部电影无疑很愚蠢的站在了两端的中间，是换一种方式的对观众的讨好。就像人一直在温水里泡着，每次加一点温水或者冷水对皮肤的冲击并不会很大，但是把人拎出来扔进冷水里，他恐怕会跳起来。这就是这部电影达到的效果，所以他的目的是近乎完美的达到了，用一个微观世界数字的成本吸引了足够多的眼球。而IMDB竟然给出了瞠目结舌的分数，这就很能够说明什么才能吸引观众，也很能说明美国观众和美国化观众对于电影的品位。人们都很厌倦日复一日的重复，都期待新鲜刺激。这就是《这个男人来自地球》存在的原因

好吧说说电影本身，我觉得如果我换上消费电影的思路来看这部电影，它也不十分成功，首先导演根本不知道一个活了14000年的人到底是什么样子，于是他用了正常人的物理特征正常人的思辩方式，或许像导演自己。另外，我难以说出哪怕一点从生理学和以多小的概率逃过14000年的天灾人祸而存活下来的可行性，这里面的破绽就不细究了，我没有说出一个很让人信服的地方，但我相信有不少。最后的高潮，算是给我一个安慰，好在导演有自知之明，好在这一刻陶渊明灵魂附体：“既出，得其船，便扶向路，处处志之。及郡下，诣太守,说如此。太守即遣人随其往，寻向所志，遂迷,不复得路。”还要加上点笔画说明一下：这是部科幻片！

]]>

written at 2007-12-13 21:27:48

2008-01-30 20:49:58

2008-10-29T08:25:00.054+08:00

1.30

昨天被妹妹翻出来一本初中同学的联系册，本来颇为恼火，后来自己看了看觉得有趣之处甚多

摘抄一些：

左哲（米猪）：皇家马德里万岁，阿狗，记住，皇马5.3号4：3大胜曼联。上海申花！游戏！每月一封邮件（从来没做到过，我很惭愧）

美丽可爱的殷晓弦

郭勉：拜仁天下无敌

（以下省略阵容1-34号）

陈龙：注意：上面的人才是U，背面的人是S'S

吴晓旭：董诣，希望你在那边把PS玩好，不要回来又被我菜！BYE!

大鳖：（省略拜仁阵容若干，但是画了个很精致的拜仁队徽）

余晓阳：上海是中国的希望，你是上海的希望（第二次惭愧）

刘立：三年后，上海高考状元就靠你提提了（这个。。。）

张晨穆：阿狗（让我最后一次这么称呼你）和你做了两年同桌，觉得你是个很温顺的男生，并不像印象中刻薄的上海人，希望不要改变。祝你在上海生活的快乐，记得给我发消息！切记（这个无比惭愧）

张智余：奉天承运，教主诏曰：亲爱的光明左使，你为光大我邪教声誉，远赴上海发展邪教事业，特赐你金山游侠III一件，FPE2000一件，东方不败一件，望你持此三样宝物，在上海打遍天下无敌手，开创我邪教之上海分舵

刘翼：望董诣能在上海看到申花夺冠和中国出线，祝学无止境（谢谢，我都看到了，但也不像以前那样再去关心中国足球，学无止境，我尽量）

王伟旗：祝你在上海活得愉快，玩的愉快，争取加入UBI公司，要BOSS还我一个练妖壶，祝你早日找到知心朋友和游戏死党（我确实给UBI投简历的时候想到了你，不过关于知心朋友，确实比较一言难尽）

刘春翔：董诣，快去申请一个OICQ号，到CHINAREN发个帖子给我！祝你在上海养只宠物，最好是个小母狗。。。。

张伟：以后多联系，师父（我也很惭愧）

彭伟：祝成绩越来越优秀，考上上海交大（惭愧again）

肖腾飞：祝你在上海考上一所理想的大学，后会有期

白帆：我没什么好给你的也不知道上海人爱不爱玩什么足球游戏，因此我只能希望以后能去上海看看你，在申花夺冠的那一天。祝学业有成，修改功夫大成

周全：到那边之后给我发帖子，记住。祝你一路顺风，永远幸福，你永远的good friend

彭地：亲爱的左使，虽然你马上就要离开这里，但一定要记住我们以前并肩作战的日子，到了上海一定要坚持以前的作风，扩大邪教在上海滩的势力，另外，祝左使仙福永享，寿与天齐

]]>

written at 2008-01-30 20:49:58

2008-05-02 20:10:02

2008-10-29T08:25:00.053+08:00

娱乐时代

早上坐公车耳塞里出来eyes on me的时候车窗外头正烈日混杂飞尘，想了想第一次听到这歌的时候到现在也有个七八年了。那时候我的梦想是将来能去做游戏，虽然现在身不由己的做了很多很多我当时都不了解的东西，但我还是庆幸我仍然没有远离这个梦想。去年投简历的时候见到UBI，是我写的最认真的一份简历。可是没有出乎意料的石沉大海，但带给我的是如同今天的一点点怀念。

过去的日子总是值得怀念，eyes on me是初中毕业的时候玩FF8第一次听到的，但是第二次玩才明白人物关系，little bar,士兵,歌女，曾经我任性的认为这是我的一切，还有哪些武侠传奇。我也会整体跟同学谈这些。现在想想那也是觉得游戏的世界比现实美好，所以我讨厌短剧情游戏让我始终在告别

如今我都忘了上一次玩游戏的时候了，自己的电脑也永远是一种最平常的主题，winblind,style那都是过去了，听歌都windows media player,wimap,foobar成了过去，那些娱乐时代，那个浪漫时期，我是不是已经忘了

]]>

written at 2008-05-02 20:10:02

2008-04-19 13:27:29

2008-10-29T08:25:00.051+08:00

4.19

上周关键字的项目正到焦头烂额的时候经理从海南回来了

我心里还有点忐忑没想到竟然跟我说给我加薪了哈哈哈哈

崩溃小黑屋住了一个星期除了没网其他都不错很爽很嗨皮

又按耐不住买书欲去当当买乐三本书编程珠玑是英文版的

UBUNTU 8.04终于出来了等下格式化正式抛弃瘟都死了

]]>

written at 2008-04-19 13:27:29

2008-04-04 09:31:04

2008-10-29T08:25:00.049+08:00

4.4

昨天开了一下午的会，讨论关键字系统的详细设计，这也是我第一次参与系统的设计。确实还是发现了很多以前从来没有想过的问题，最主要是同步问题，。要考虑多台机器多个CPU可能造成的读写同步。要求我们三个菜鸟做出来这个系统其实也难度不小，整体的负载大约每秒几千次请求。服务器大约4-10台的样子，而且给电信做东西，系统一上线就要要求能够连续跑半年到一年没有BUG。现在概要设计和详细设计基本完成了。其实我们几个对python还没有完全掌握，实现可能也会碰到很多问题，还有sqlalchemy,memcache要学。谢特

]]>

written at 2008-04-04 09:31:04

2008-03-31 22:03:53

2008-10-29T08:25:00.047+08:00

3.31

我爱星期一，我讨厌星期五

春天到了，大家都在发春，我也有点蛋蛋的忧伤，为什么王菲选择了李亚鹏，而不是我！

]]>

written at 2008-03-31 22:03:53

2008-03-25 22:40:08

2008-10-29T08:25:00.045+08:00

3.25

我看来需要一点计划：

长期内至少每天看10页的代码大全，每天要有足够的无氧运动，每周至少两次足够的有氧运动

这周内：

下个win2000好好把工作环境搭起来，受不了vista的安全机制了，然后ubuntu又认不出蓝牙又十分恶心的不等宽字体，没办法，没有win2000后面的什么都干不了

]]>

written at 2008-03-25 22:40:08

2008-03-25 11:26:24

2008-10-29T08:25:00.043+08:00

3.25

说几样能让我心里颤动一下的东西：一样是几米的漫画，印象最深的一本是布瓜的世界，很多页我都觉得我在画面里。还有是香港的电影，我还是那一代看着港剧长大的小孩，所以最让我心动不已的电影不是欧洲文艺片不是王家卫不是美国片，像英雄本色阿朗故事麦兜这些才是，纯粹的不要考虑很多的感动。还有就是有时候看到这个吵闹城市繁华的夜景，但又时时感到不知我站在何地，伴随着恐惧感。另外我想谈恋爱也算，但是回想起来又觉得里面心烦意乱远胜于喜悦激动，但凡是人类活动哪个不是用多数的忍耐煎熬痛苦疲惫换取一点点心里悸动和快感。

抬头瞄了一下341篇日志 / 344条评论

]]>

written at 2008-03-25 11:26:24

2008-03-22 21:49:03

2008-10-29T08:25:00.041+08:00

3.22

被MMT点名，囧囧囧囧

1.如果你很崇拜一个人（生活里见得到的活人），你对他/她会有什么特别的反应？

假装不把他放在心上，让他没有压力

2.你是一个有同情心的人吗？

非常有

3.此时此刻最想做什么？（此时此刻的时间间隔为2～3s）

吃橘子

4.这段时间最想做什么（时间间隔为1～2个月）

没有什么目标

5.你习惯凝视你亲密的人的眼睛吗？

习惯

6.现在电脑的桌面是什么？

风景，草原

7.喜欢自己睡还是跟人一起睡？

一个人把

8.上网的时候有什么特别的习惯吗？

躺着用无线鼠标在被子里点，并行的干很多事情

9.你最不可思议的朋友？（觉得最不可能成为朋友却成了朋友的）
以前是朋友后来他成牛人了的太多了，这个不算的话，还真想不出来几个

10.说说你眼里的我吧～
很有趣很勇敢的女人

继续点名，我也不知道有几个人会看我的页面

大姚，阿K，老婷，

]]>

written at 2008-03-22 21:49:03

2008-03-21 23:57:42

2008-10-29T08:25:00.039+08:00

3.21

在张江三周了，很喜欢这个地方，不喜欢回家。发觉我在慢慢丧失仅有的那么一点点语言能力了，用手指说话远远比用嘴流利，蟹特。在张江一个人住我也半夜看恐怖片，但是每天早上起来都觉得人生TMD无望

大姚要去日本了，美好生活等着他。托老哥从美国带回来的iphone这两天一直在捣腾，估计新鲜感也不会太久。pdf看起来太麻烦

这两天在看django框架，目前看的有点眉目就在看同事做的一个小东西，发现同事是个大牛人啊，现在还没毕业，我很惭愧。我还得跑几年龙套

]]>

written at 2008-03-21 23:57:42

2008-03-12 09:00:04

2008-10-29T08:25:00.037+08:00

3.12

I need a real change

早上说的不靠谱

每天半小时英语一定要看，运动够数即可

坚持21天

否则永远找不到老婆

]]>

written at 2008-03-12 09:00:04

2008-03-11 22:04:47

2008-10-29T08:25:00.035+08:00

3.11

今天写好了平衡二叉树，删除部分搞了半天都不对只好弄了个开销高的办法，每次调整都计算左右子树的高度来确定是不是平衡，囧，不过好在能用了，插入部分应该性能是不错的。代码还需要整理一下，基本一行注释也没有，为啥我总是对好不容易写好的东西这么厌恶呢，想搞新的东西

今天考研分数出来，几人欢喜几人忧，阿毛330多，应该没啥问题，潜水艇360，祝福了，再差也能调剂到上大。我不想翻去年写的博了。其实并没有什么是可以不惜一切坚持的。

原来觉得在很多群体里我都是比较小的一个，现在猛的发现情况就反过来了，时间不知不觉的慢慢的溜过去，并且在某个时间我们突然发现。我还有好多事情没有做，说的少，做的更少。皈依的事情拖了好久，现在看来好像也比较难办，一个人住还是挺开心的，没什么杂念，就是有点点想念宏基的阿康烧烤

]]>

written at 2008-03-11 22:04:47

2008-03-05 23:54:53

2008-10-29T08:25:00.033+08:00

The Humble Programmer

ACM Turing Lecture 1972

EWD340

The Humble Programmer
by
Edsger W. Dijkstra

As a result of a long sequence of coincidences I entered the programming profession officially on the first spring morning of 1952 and as far as I have been able to trace, I was the first Dutchman to do so in my country. In retrospect the most amazing thing was the slowness with which, at least in my part of the world, the programming profession emerged, a slowness which is now hard to believe. But I am grateful for two vivid recollections from that period that establish that slowness beyond any doubt.

After having programmed for some three years, I had a discussion with A. van Wijngaarden, who was then my boss at the Mathematical Centre in Amsterdam, a discussion for which I shall remain grateful to him as long as I live. The point was that I was supposed to study theoretical physics at the University of Leiden simultaneously, and as I found the two activities harder and harder to combine, I had to make up my mind, either to stop programming and become a real, respectable theoretical physicist, or to carry my study of physics to a formal completion only, with a minimum of effort, and to become....., yes what? A programmer? But was that a respectable profession? For after all, what was programming? Where was the sound body of knowledge that could support it as an intellectually respectable discipline? I remember quite vividly how I envied my hardware colleagues, who, when asked about their professional competence, could at least point out that they knew everything about vacuum tubes, amplifiers and the rest, whereas I felt that, when faced with that question, I would stand empty-handed. Full of misgivings I knocked on van Wijngaarden's office door, asking him whether I could "speak to him for a moment"; when I left his office a number of hours later, I was another person. For after having listened to my problems patiently, he agreed that up till that moment there was not much of a programming discipline, but then he went on to explain quietly that automatic computers were here to stay, that we were just at the beginning and could not I be one of the persons called to make programming a respectable discipline in the years to come? This was a turning point in my life and I completed my study of physics formally as quickly as I could. One moral of the above story is, of course, that we must be very careful when we give advice to younger people; sometimes they follow it!

Another two years later, in 1957, I married and Dutch marriage rites require you to state your profession and I stated that I was a programmer. But the municipal authorities of the town of Amsterdam did not accept it on the grounds that there was no such profession. And, believe it or not, but under the heading "profession" my marriage act shows the ridiculous entry "theoretical physicist"!

So much for the slowness with which I saw the programming profession emerge in my own country. Since then I have seen more of the world, and it is my general impression that in other countries, apart from a possible shift of dates, the growth pattern has been very much the same.

Let me try to capture the situation in those old days in a little bit more detail, in the hope of getting a better understanding of the situation today. While we pursue our analysis, we shall see how many common misunderstandings about the true nature of the programming task can be traced back to that now distant past.

The first automatic electronic computers were all unique, single-copy machines and they were all to be found in an environment with the exciting flavour of an experimental laboratory. Once the vision of the automatic computer was there, its realisation was a tremendous challenge to the electronic technology then available, and one thing is certain: we cannot deny the courage of the groups that decided to try and build such a fantastic piece of equipment. For fantastic pieces of equipment they were: in retrospect one can only wonder that those first machines worked at all, at least sometimes. The overwhelming problem was to get and keep the machine in working order. The preoccupation with the physical aspects of automatic computing is still reflected in the names of the older scientific societies in the field, such as the Association for Computing Machinery or the British Computer Society, names in which explicit reference is made to the physical equipment.

What about the poor programmer? Well, to tell the honest truth: he was hardly noticed. For one thing, the first machines were so bulky that you could hardly move them and besides that, they required such extensive maintenance that it was quite natural that the place where people tried to use the machine was the same laboratory where the machine had been developed. Secondly, his somewhat invisible work was without any glamour: you could show the machine to visitors and that was several orders of magnitude more spectacular than some sheets of coding. But most important of all, the programmer himself had a very modest view of his own work: his work derived all its significance from the existence of that wonderful machine. Because that was a unique machine, he knew only too well that his programs had only local significance and also, because it was patently obvious that this machine would have a limited lifetime, he knew that very little of his work would have a lasting value. Finally, there is yet another circumstance that had a profound influence on the programmer's attitude to his work: on the one hand, besides being unreliable, his machine was usually too slow and its memory was usually too small, i.e. he was faced with a pinching shoe, while on the other hand its usually somewhat queer order code would cater for the most unexpected constructions. And in those days many a clever programmer derived an immense intellectual satisfaction from the cunning tricks by means of which he contrived to squeeze the impossible into the constraints of his equipment.

Two opinions about programming date from those days. I mention them now, I shall return to them later. The one opinion was that a really competent programmer should be puzzle-minded and very fond of clever tricks; the other opinon was that programming was nothing more than optimizing the efficiency of the computational process, in one direction or the other.

The latter opinion was the result of the frequent circumstance that, indeed, the available equipment was a painfully pinching shoe, and in those days one often encountered the naive expectation that, once more powerful machines were available, programming would no longer be a problem, for then the struggle to push the machine to its limits would no longer be necessary and that was all what programming was about, wasn't it? But in the next decades something completely different happened: more powerful machines became available, not just an order of magnitude more powerful, even several orders of magnitude more powerful. But instead of finding ourselves in the state of eternal bliss of all progamming problems solved, we found ourselves up to our necks in the software crisis! How come?

There is a minor cause: in one or two respects modern machinery is basically more difficult to handle than the old machinery. Firstly, we have got the I/O interrupts, occurring at unpredictable and irreproducible moments; compared with the old sequential machine that pretended to be a fully deterministic automaton, this has been a dramatic change and many a systems programmer's grey hair bears witness to the fact that we should not talk lightly about the logical problems created by that feature. Secondly, we have got machines equipped with multi-level stores, presenting us problems of management strategy that, in spite of the extensive literature on the subject, still remain rather elusive. So much for the added complication due to structural changes of the actual machines.

But I called this a minor cause; the major cause is... that the machines have become several orders of magnitude more powerful! To put it quite bluntly: as long as there were no machines, programming was no problem at all; when we had a few weak computers, programming became a mild problem, and now we have gigantic computers, programming had become an equally gigantic problem. In this sense the electronic industry has not solved a single problem, it has only created them, it has created the problem of using its products. To put it in another way: as the power of available machines grew by a factor of more than a thousand, society's ambition to apply these machines grew in proportion, and it was the poor programmer who found his job in this exploded field of tension between ends and means. The increased power of the hardware, together with the perhaps even more dramatic increase in its reliability, made solutions feasible that the programmer had not dared to dream about a few years before. And now, a few years later, he had to dream about them and, even worse, he had to transform such dreams into reality! Is it a wonder that we found ourselves in a software crisis? No, certainly not, and as you may guess, it was even predicted well in advance; but the trouble with minor prophets, of course, is that it is only five years later that you really know that they had been right.

Then, in the mid-sixties, something terrible happened: the computers of the so-called third generation made their appearance. The official literature tells us that their price/performance ratio has been one of the major design objectives. But if you take as "performance" the duty cycle of the machine's various components, little will prevent you from ending up with a design in which the major part of your performance goal is reached by internal housekeeping activities of doubtful necessity. And if your definition of price is the price to be paid for the hardware, little will prevent you from ending up wth a design that is terribly hard to program for: for instance the order code might be such as to enforce, either upon the progrmmer or upon the system, early binding decisions presenting conflicts that really cannot be resolved. And to a large extent these unpleasant possibilities seem to have become reality.

When these machines were announced and their functional specifications became known, quite a few among us must have become quite miserable; at least I was. It was only reasonable to expect that such machines would flood the computing community, and it was therefore all the more important that their design should be as sound as possible. But the design embodied such serious flaws that I felt that with a single stroke the progress of computing science had been retarded by at least ten years: it was then that I had the blackest week in the whole of my professional life. Perhaps the most saddening thing now is that, even after all those years of frustrating experience, still so many people honestly believe that some law of nature tells us that machines have to be that way. They silence their doubts by observing how many of these machines have been sold, and derive from that observation the false sense of security that, after all, the design cannot have been that bad. But upon closer inspection, that line of defense has the same convincing strength as the argument that cigarette smoking must be healthy because so many people do it.

It is in this connection that I regret that it is not customary for scientific journals in the computing area to publish reviews of newly announced computers in much the same way as we review scientific publications: to review machines would be at least as important. And here I have a confession to make: in the early sixties I wrote such a review with the intention of submitting it to the CACM, but in spite of the fact that the few colleagues to whom the text was sent for their advice, urged me all to do so, I did not dare to do it, fearing that the difficulties either for myself or for the editorial board would prove to be too great. This suppression was an act of cowardice on my side for which I blame myself more and more. The difficulties I foresaw were a consequence of the absence of generally accepted criteria, and although I was convinced of the validity of the criteria I had chosen to apply, I feared that my review would be refused or discarded as "a matter of personal taste". I still think that such reviews would be extremely useful and I am longing to see them appear, for their accepted appearance would be a sure sign of maturity of the computing community.

The reason that I have paid the above attention to the hardware scene is because I have the feeling that one of the most important aspects of any computing tool is its influence on the thinking habits of those that try to use it, and because I have reasons to believe that that influence is many times stronger than is commonly assumed. Let us now switch our attention to the software scene.

Here the diversity has been so large that I must confine myself to a few stepping stones. I am painfully aware of the arbitrariness of my choice and I beg you not to draw any conclusions with regard to my appreciation of the many efforts that will remain unmentioned.

In the beginning there was the EDSAC in Cambridge, England, and I think it quite impressive that right from the start the notion of a subroutine library played a central role in the design of that machine and of the way in which it should be used. It is now nearly 25 years later and the computing scene has changed dramatically, but the notion of basic software is still with us, and the notion of the closed subroutine is still one of the key concepts in programming. We should recognise the closed subroutines as one of the greatest software inventions; it has survived three generations of computers and it will survive a few more, because it caters for the implementation of one of our basic patterns of abstraction. Regrettably enough, its importance has been underestimated in the design of the third generation computers, in which the great number of explicitly named registers of the arithmetic unit implies a large overhead on the subroutine mechanism. But even that did not kill the concept of the subroutine, and we can only pray that the mutation won't prove to be hereditary.

The second major development on the software scene that I would like to mention is the birth of FORTRAN. At that time this was a project of great temerity and the people responsible for it deserve our great admiration. It would be absolutely unfair to blame them for shortcomings that only became apparent after a decade or so of extensive usage: groups with a successful look-ahead of ten years are quite rare! In retrospect we must rate FORTRAN as a successful coding technique, but with very few effective aids to conception, aids which are now so urgently needed that time has come to consider it out of date. The sooner we can forget that FORTRAN has ever existed, the better, for as a vehicle of thought it is no longer adequate: it wastes our brainpower, is too risky and therefore too expensive to use. FORTRAN's tragic fate has been its wide acceptance, mentally chaining thousands and thousands of programmers to our past mistakes. I pray daily that more of my fellow-programmers may find the means of freeing themselves from the curse of compatibility.

The third project I would not like to leave unmentioned is LISP, a fascinating enterprise of a completely different nature. With a few very basic principles at its foundation, it has shown a remarkable stability. Besides that, LISP has been the carrier for a considerable number of in a sense our most sophisticated computer applications. LISP has jokingly been described as "the most intelligent way to misuse a computer". I think that description a great compliment because it transmits the full flavour of liberation: it has assisted a number of our most gifted fellow humans in thinking previously impossible thoughts.

The fourth project to be mentioned is ALGOL 60. While up to the present day FORTRAN programmers still tend to understand their programming language in terms of the specific implementation they are working with —hence the prevalence of octal and hexadecimal dumps—, while the definition of LISP is still a curious mixture of what the language means and how the mechanism works, the famous Report on the Algorithmic Language ALGOL 60 is the fruit of a genuine effort to carry abstraction a vital step further and to define a programming language in an implementation-independent way. One could argue that in this respect its authors have been so successful that they have created serious doubts as to whether it could be implemented at all! The report gloriously demonstrated the power of the formal method BNF, now fairly known as Backus-Naur-Form, and the power of carefully phrased English, a least when used by someone as brilliant as Peter Naur. I think that it is fair to say that only very few documents as short as this have had an equally profound influence on the computing community. The ease with which in later years the names ALGOL and ALGOL-like have been used, as an unprotected trade mark, to lend some of its glory to a number of sometimes hardly related younger projects, is a somewhat shocking compliment to its standing. The strength of BNF as a defining device is responsible for what I regard as one of the weaknesses of the language: an over-elaborate and not too systematic syntax could now be crammed into the confines of very few pages. With a device as powerful as BNF, the Report on the Algorithmic Language ALGOL 60 should have been much shorter. Besides that I am getting very doubtful about ALGOL 60's parameter mechanism: it allows the programmer so much combinatorial freedom, that its confident use requires a strong discipline from the programmer. Besides expensive to implement it seems dangerous to use.

Finally, although the subject is not a pleasant one, I must mention PL/1, a programming language for which the defining documentation is of a frightening size and complexity. Using PL/1 must be like flying a plane with 7000 buttons, switches and handles to manipulate in the cockpit. I absolutely fail to see how we can keep our growing programs firmly within our intellectual grip when by its sheer baroqueness the programming language —our basic tool, mind you!— already escapes our intellectual control. And if I have to describe the influence PL/1 can have on its users, the closest metaphor that comes to my mind is that of a drug. I remember from a symposium on higher level programming language a lecture given in defense of PL/1 by a man who described himself as one of its devoted users. But within a one-hour lecture in praise of PL/1. he managed to ask for the addition of about fifty new "features", little supposing that the main source of his problems could very well be that it contained already far too many "features". The speaker displayed all the depressing symptoms of addiction, reduced as he was to the state of mental stagnation in which he could only ask for more, more, more... When FORTRAN has been called an infantile disorder, full PL/1, with its growth characteristics of a dangerous tumor, could turn out to be a fatal disease.

So much for the past. But there is no point in making mistakes unless thereafter we are able to learn from them. As a matter of fact, I think that we have learned so much, that within a few years programming can be an activity vastly different from what it has been up till now, so different that we had better prepare ourselves for the shock. Let me sketch for you one of the posssible futures. At first sight, this vision of programming in perhaps already the near future may strike you as utterly fantastic. Let me therefore also add the considerations that might lead one to the conclusion that this vision could be a very real possibility.

The vision is that, well before the seventies have run to completion, we shall be able to design and implement the kind of systems that are now straining our programming ability, at the expense of only a few percent in man-years of what they cost us now, and that besides that, these systems will be virtually free of bugs. These two improvements go hand in hand. In the latter respect software seems to be different from many other products, where as a rule a higher quality implies a higher price. Those who want really reliable software will discover that they must find means of avoiding the majority of bugs to start with, and as a result the programming process will become cheaper. If you want more effective programmers, you will discover that they should not waste their time debugging, they should not introduce the bugs to start with. In other words: both goals point to the same change.

Such a drastic change in such a short period of time would be a revolution, and to all persons that base their expectations for the future on smooth extrapolation of the recent past —appealing to some unwritten laws of social and cultural inertia— the chance that this drastic change will take place must seem negligible. But we all know that sometimes revolutions do take place! And what are the chances for this one?

There seem to be three major conditions that must be fulfilled. The world at large must recognize the need for the change; secondly the economic need for it must be sufficiently strong; and, thirdly, the change must be technically feasible. Let me discuss these three conditions in the above order.

With respect to the recognition of the need for greater reliability of software, I expect no disagreement anymore. Only a few years ago this was different: to talk about a software crisis was blasphemy. The turning point was the Conference on Software Engineering in Garmisch, October 1968, a conference that created a sensation as there occured the first open admission of the software crisis. And by now it is generally recognized that the design of any large sophisticated system is going to be a very difficult job, and whenever one meets people responsible for such undertakings, one finds them very much concerned about the reliability issue, and rightly so. In short, our first condition seems to be satisfied.

Now for the economic need. Nowadays one often encounters the opinion that in the sixties programming has been an overpaid profession, and that in the coming years programmer salaries may be expected to go down. Usually this opinion is expressed in connection with the recession, but it could be a symptom of something different and quite healthy, viz. that perhaps the programmers of the past decade have not done so good a job as they should have done. Society is getting dissatisfied with the performance of programmers and of their products. But there is another factor of much greater weight. In the present situation it is quite usual that for a specific system, the price to be paid for the development of the software is of the same order of magnitude as the price of the hardware needed, and society more or less accepts that. But hardware manufacturers tell us that in the next decade hardware prices can be expected to drop with a factor of ten. If software development were to continue to be the same clumsy and expensive process as it is now, things would get completely out of balance. You cannot expect society to accept this, and therefore we must learn to program an order of magnitude more effectively. To put it in another way: as long as machines were the largest item on the budget, the programming profession could get away with its clumsy techniques, but that umbrella will fold rapidly. In short, also our second condition seems to be satisfied.

And now the third condition: is it technically feasible? I think it might and I shall give you six arguments in support of that opinion.

A study of program structure had revealed that programs —even alternative programs for the same task and with the same mathematical content— can differ tremendously in their intellectual manageability. A number of rules have been discovered, violation of which will either seriously impair or totally destroy the intellectual manageability of the program. These rules are of two kinds. Those of the first kind are easily imposed mechanically, viz. by a suitably chosen programming language. Examples are the exclusion of goto-statements and of procedures with more than one output parameter. For those of the second kind I at least —but that may be due to lack of competence on my side— see no way of imposing them mechanically, as it seems to need some sort of automatic theorem prover for which I have no existence proof. Therefore, for the time being and perhaps forever, the rules of the second kind present themselves as elements of discipline required from the programmer. Some of the rules I have in mind are so clear that they can be taught and that there never needs to be an argument as to whether a given program violates them or not. Examples are the requirements that no loop should be written down without providing a proof for termination nor without stating the relation whose invariance will not be destroyed by the execution of the repeatable statement.

I now suggest that we confine ourselves to the design and implementation of intellectually manageable programs. If someone fears that this restriction is so severe that we cannot live with it, I can reassure him: the class of intellectually manageable programs is still sufficiently rich to contain many very realistic programs for any problem capable of algorithmic solution. We must not forget that it is not our business to make programs, it is our business to design classes of computations that will display a desired behaviour. The suggestion of confining ourselves to intellectually manageable programs is the basis for the first two of my announced six arguments.

Argument one is that, as the programmer only needs to consider intellectually manageable programs, the alternatives he is choosing between are much, much easier to cope with.

Argument two is that, as soon as we have decided to restrict ourselves to the subset of the intellectually manageable programs, we have achieved, once and for all, a drastic reduction of the solution space to be considered. And this argument is distinct from argument one.

Argument three is based on the constructive approach to the problem of program correctness. Today a usual technique is to make a program and then to test it. But: program testing can be a very effective way to show the presence of bugs, but is hopelessly inadequate for showing their absence. The only effective way to raise the confidence level of a program significantly is to give a convincing proof of its correctness. But one should not first make the program and then prove its correctness, because then the requirement of providing the proof would only increase the poor programmer's burden. On the contrary: the programmer should let correctness proof and program grow hand in hand. Argument three is essentially based on the following observation. If one first asks oneself what the structure of a convincing proof would be and, having found this, then constructs a program satisfying this proof's requirements, then these correctness concerns turn out to be a very effective heuristic guidance. By definition this approach is only applicable when we restrict ourselves to intellectually manageable programs, but it provides us with effective means for finding a satisfactory one among these.

Argument four has to do with the way in which the amount of intellectual effort needed to design a program depends on the program length. It has been suggested that there is some kind of law of nature telling us that the amount of intellectual effort needed grows with the square of program length. But, thank goodness, no one has been able to prove this law. And this is because it need not be true. We all know that the only mental tool by means of which a very finite piece of reasoning can cover a myriad cases is called "abstraction"; as a result the effective exploitation of his powers of abstraction must be regarded as one of the most vital activities of a competent programmer. In this connection it might be worth-while to point out that the purpose of abstracting is not to be vague, but to create a new semantic level in which one can be absolutely precise. Of course I have tried to find a fundamental cause that would prevent our abstraction mechanisms from being sufficiently effective. But no matter how hard I tried, I did not find such a cause. As a result I tend to the assumption —up till now not disproved by experience— that by suitable application of our powers of abstraction, the intellectual effort needed to conceive or to understand a program need not grow more than proportional to program length. But a by-product of these investigations may be of much greater practical significance, and is, in fact, the basis of my fourth argument. The by-product was the identification of a number of patterns of abstraction that play a vital role in the whole process of composing programs. Enough is now known about these patterns of abstraction that you could devote a lecture to about each of them. What the familiarity and conscious knowledge of these patterns of abstraction imply dawned upon me when I realized that, had they been common knowledge fifteen years ago, the step from BNF to syntax-directed compilers, for instance, could have taken a few minutes instead of a few years. Therefore I present our recent knowledge of vital abstraction patterns as the fourth argument.

Now for the fifth argument. It has to do with the influence of the tool we are trying to use upon our own thinking habits. I observe a cultural tradition, which in all probability has its roots in the Renaissance, to ignore this influence, to regard the human mind as the supreme and autonomous master of its artefacts. But if I start to analyse the thinking habits of myself and of my fellow human beings, I come, whether I like it or not, to a completely different conclusion, viz. that the tools we are trying to use and the language or notation we are using to express or record our thoughts, are the major factors determining what we can think or express at all! The analysis of the influence that programming languages have on the thinking habits of its users, and the recognition that, by now, brainpower is by far our scarcest resource, they together give us a new collection of yardsticks for comparing the relative merits of various programming languages. The competent programmer is fully aware of the strictly limited size of his own skull; therefore he approaches the programming task in full humility, and among other things he avoids clever tricks like the plague. In the case of a well-known conversational programming language I have been told from various sides that as soon as a programming community is equipped with a terminal for it, a specific phenomenon occurs that even has a well-established name: it is called "the one-liners". It takes one of two different forms: one programmer places a one-line program on the desk of another and either he proudly tells what it does and adds the question "Can you code this in less symbols?" —as if this were of any conceptual relevance!— or he just asks "Guess what it does!". From this observation we must conclude that this language as a tool is an open invitation for clever tricks; and while exactly this may be the explanation for some of its appeal, viz. to those who like to show how clever they are, I am sorry, but I must regard this as one of the most damning things that can be said about a programming language. Another lesson we should have learned from the recent past is that the development of "richer" or "more powerful" programming languages was a mistake in the sense that these baroque monstrosities, these conglomerations of idiosyncrasies, are really unmanageable, both mechanically and mentally. I see a great future for very systematic and very modest programming languages. When I say "modest", I mean that, for instance, not only ALGOL 60's "for clause", but even FORTRAN's "DO loop" may find themselves thrown out as being too baroque. I have run a a little programming experiment with really experienced volunteers, but something quite unintended and quite unexpected turned up. None of my volunteers found the obvious and most elegant solution. Upon closer analysis this turned out to have a common source: their notion of repetition was so tightly connected to the idea of an associated controlled variable to be stepped up, that they were mentally blocked from seeing the obvious. Their solutions were less efficient, needlessly hard to understand, and it took them a very long time to find them. It was a revealing, but also shocking experience for me. Finally, in one respect one hopes that tomorrow's programming languages will differ greatly from what we are used to now: to a much greater extent than hitherto they should invite us to reflect in the structure of what we write down all abstractions needed to cope conceptually with the complexity of what we are designing. So much for the greater adequacy of our future tools, which was the basis of the fifth argument.

As an aside I would like to insert a warning to those who identify the difficulty of the programming task with the struggle against the inadequacies of our current tools, because they might conclude that, once our tools will be much more adequate, programming will no longer be a problem. Programming will remain very difficult, because once we have freed ourselves from the circumstantial cumbersomeness, we will find ourselves free to tackle the problems that are now well beyond our programming capacity.

You can quarrel with my sixth argument, for it is not so easy to collect experimental evidence for its support, a fact that will not prevent me from believing in its validity. Up till now I have not mentioned the word "hierarchy", but I think that it is fair to say that this is a key concept for all systems embodying a nicely factored solution. I could even go one step further and make an article of faith out of it, viz. that the only problems we can really solve in a satisfactory manner are those that finally admit a nicely factored solution. At first sight this view of human limitations may strike you as a rather depressing view of our predicament, but I don't feel it that way, on the contrary! The best way to learn to live with our limitations is to know them. By the time that we are sufficiently modest to try factored solutions only, because the other efforts escape our intellectual grip, we shall do our utmost best to avoid all those interfaces impairing our ability to factor the system in a helpful way. And I cannot but expect that this will repeatedly lead to the discovery that an initially untractable problem can be factored after all. Anyone who has seen how the majority of the troubles of the compiling phase called "code generation" can be tracked down to funny properties of the order code, will know a simple example of the kind of things I have in mind. The wider applicability of nicely factored solutions is my sixth and last argument for the technical feasibiilty of the revolution that might take place in the current decade.

In principle I leave it to you to decide for yourself how much weight you are going to give to my considerations, knowing only too well that I can force no one else to share my beliefs. As each serious revolution, it will provoke violent opposition and one can ask oneself where to expect the conservative forces trying to counteract such a development. I don't expect them primarily in big business, not even in the computer business; I expect them rather in the educational institutions that provide today's training and in those conservative groups of computer users that think their old programs so important that they don't think it worth-while to rewrite and improve them. In this connection it is sad to observe that on many a university campus the choice of the central computing facility has too often been determined by the demands of a few established but expensive applications with a disregard of the question how many thousands of "small users" that are willing to write their own programs were going to suffer from this choice. Too often, for instance, high-energy physics seems to have blackmailed the scientific community with the price of its remaining experimental equipment. The easiest answer, of course, is a flat denial of the technical feasibility, but I am afraid that you need pretty strong arguments for that. No reassurance, alas, can be obtained from the remark that the intellectual ceiling of today's average programmer will prevent the revolution from taking place: with others programming so much more effectively, he is liable to be edged out of the picture anyway.

There may also be political impediments. Even if we know how to educate tomorrow's professional programmer, it is not certain that the society we are living in will allow us to do so. The first effect of teaching a methodology —rather than disseminating knowledge— is that of enhancing the capacities of the already capable, thus magnifying the difference in intelligence. In a society in which the educational system is used as an instrument for the establishment of a homogenized culture, in which the cream is prevented from rising to the top, the education of competent programmers could be politically impalatable.

Let me conclude. Automatic computers have now been with us for a quarter of a century. They have had a great impact on our society in their capacity of tools, but in that capacity their influence will be but a ripple on the surface of our culture, compared with the much more profound influence they will have in their capacity of intellectual challenge without precedent in the cultural history of mankind. Hierarchical systems seem to have the property that something considered as an undivided entity on one level, is considered as a composite object on the next lower level of greater detail; as a result the natural grain of space or time that is applicable at each level decreases by an order of magnitude when we shift our attention from one level to the next lower one. We understand walls in terms of bricks, bricks in terms of crystals, crystals in terms of molecules etc. As a result the number of levels that can be distinguished meaningfully in a hierarchical system is kind of proportional to the logarithm of the ratio between the largest and the smallest grain, and therefore, unless this ratio is very large, we cannot expect many levels. In computer programming our basic building block has an associated time grain of less than a microsecond, but our program may take hours of computation time. I do not know of any other technology covering a ratio of 10¹⁰ or more: the computer, by virtue of its fantastic speed, seems to be the first to provide us with an environment where highly hierarchical artefacts are both possible and necessary. This challenge, viz. the confrontation with the programming task, is so unique that this novel experience can teach us a lot about ourselves. It should deepen our understanding of the processes of design and creation, it should give us better control over the task of organizing our thoughts. If it did not do so, to my taste we should not deserve the computer at all!

It has already taught us a few lessons, and the one I have chosen to stress in this talk is the following. We shall do a much better programming job, provided that we approach the task with a full appreciation of its tremendous difficulty, provided that we stick to modest and elegant programming languages, provided that we respect the intrinsic limitations of the human mind and approach the task as Very Humble Programmers.

]]>

written at 2008-03-05 23:54:53

2008-03-04 20:47:24

2008-10-29T08:25:00.031+08:00

3.4

今天在家突发奇想连了一把无线，竟然就连进去一个不加密的。。RP不错，那就补上前几天的游记吧

话说冬未去春已来，一件外套安安静静在包里躺了两天。

在28号晚上之前，火车是我最喜欢的交通工具之一，本想着淡季加之春运结束，应该人不会多，可惜大大出乎所料，提前一个小时进入候车厅的时候已经坐满了人了。检票上车，一人睡两个座位的希望一点点的破灭掉，他妈的。总之最后是民工填满了所有的座位，走道还站满了。想睡睡吧，斜对面一个猥琐男眼神很奇怪，斜眼看人，心里有点不安，睡觉不踏实。想干脆不睡吧，大姚要睡，没人扯淡，没办法。最后决定两只眼睛轮流睡，后来证实了可行性也不行，耳朵不能轮流睡，只好听到几个民工在谈法拉利，肚子里偷偷的笑，然后又他妈的一只眼睛瞧见对面两个朴素的情侣在kiss，身上脸上头发上都脏兮兮的，哎。。后半夜又他妈听到旁边一个朴素小伙和一个朴素小姑娘搭讪全过程，听到这小姑娘说谈恋爱不好就换，天天换，OMG，后来听到她语气里有点不耐烦，他妈的，你自己长个包子样就别怨狗跟着

折腾了一夜，终于看到太阳了，就感觉周围的吸血鬼终于要被阳光融化了。借着日出的阳光瞥见温州，你娘，温州就一大山寨，××鞋厂，××服饰厂，××鞋厂，××服饰厂。。。下车，饥寒困交迫，浑身无力，看到路边有狗就在琢磨是骑它去旅游还是炖了吃。继续赶路，买了到雁荡山的车票，又在半睡半醒着辗转到了雁荡山。然后被个老娘们宰了一把，大概是孤太困了，脑子不清楚，中了她的宰，包了车，70块一个人，还好住宿不贵，30块一个人。早上去的山就是这个：

大概叫石头山，山上有洞，大概叫石头洞，还有石头庙，反正都差不多

更多照片请访问我的相册

没想到的是总共三个景点第一个就走了一个小时左右就回去了，怪不得只要20块钱门票，谢特。还好我学生证护体，一路半价。感谢上海大学，感谢计算机学院，感谢钱伟长

第二个景点叫做大龙湫，据说是个瀑布，我们一阵好走，来到这么个地方：

看来看去这个比较有可能曾经是瀑布了，可以歪歪的是在猴月马日，它曾经很大水，歪歪还是很美好的，但是睁开眼睛，就不得不费点劲才可以让现实和歪歪距离近一些，这是我在他脚下拍的：

这样有点像瀑布了。不那么让人沮丧的是瀑布形成的一潭清水挺不错的，水很凉很清澈：

到这里之后四处张望了一下发现没有接下去的路了，又他妈的要原路返回。想想十五块的票，还算比世纪公园好那么一点点吧，发科

中午被那个老娘们拉到一个地方吃饭，一看就是虎穴，只好点了两份炒年糕，很好，黑心十。吃饱上路，下午据说是个比较大的景点，这个时候已经有点走不动了，腿酸的要命，极度犯困。这里比早上的景点来看就是石头山少了一点，其实是树多了一点，有个高空飞车表演，我们都没有雅兴去看了，往山上爬吧

路上的山都是这个姿势的：

到山顶，终于断肠了一回，我断腿了

这个是古墓，可惜进去要钱，我说拜师行不行啊？拜师也要钱进去

世道是不咋好，抬头望见一面黄色锦旗，书“替天行道”四字。

顿时我仿佛看见一群大汉递给我酒来，曰喝，我们除暴安良劫富济贫，杀尽天下该杀之人，兄台你若不嫌弃，俺们来这聚义厅一聚。我提了提裤腰带正抖擞精神迈开腿上台阶，猛听见脑后一个断肠的声音“上去在这里买票”

操

回到小旅馆，才下午3点多，没办法只好买了个柚子边吃边看脑残电视剧，我他妈的不远千里冒着自己断腿的危险,放弃了在家宅着的机会来到这鸟不拉屎的地方看脑残电视剧住脑残旅馆，是多么的毫不利己,专门利人,对旅游的极端的负责任,对祖国大好河山极端的热爱啊～是怎样的一种省际主义精神！

晚上又他妈的崩溃了一回，去看那短命的灵峰夜景，老娘们说十点以后去不用门票，我想想十点他们灯都关了看个屁啊，一边沉醉在一种智商上的优越感中一边屁颠屁颠去了，还蹭了个导游，去了才知道，你娘，八点也不开灯，其实根本没灯，导游果然都是过了歪歪专业十级的，“大家顺着我的灯光看这座山峰，在晚上就像一个×××，而在白天，他是一个×××” 。你抢了我的钱，让我快断了腿，还侮辱了我的智商，操

还好睡了个觉，第二天准备回去了，顺便在杭州转转，发现一个规律，杭州美美都是大饼脸，后来到了西湖边上发现一些例外，还不错。断桥上走了走，非常没劲，跟前几次看杭州也没有太大差别

最后最后，坐了一把动车，尝了个新鲜。。。

]]>

written at 2008-03-04 20:47:24

2008-03-04 22:09:30

2008-10-29T08:25:00.029+08:00

3.4

新工作两天了，这两天都在学python，昨天看了一天教材，感觉进度有点慢，今天开始用迭代的方法，迅速看了余下的一些重要章节，开始做题，做了一个单链表数据结构，刚开始有点不习惯，第一次用动态类型语言，但又是强类型的。用变量前总在不放心它没有类型没声明过没定义过，但是后来用起来还挺顺手，不错不错，慢慢来，明天再看看二叉树。加油加油

工作环境我不能更满意了，食堂，小图书库，很大的个人空间，充足的阳光空气，融洽的环境。老板和经理也都不错，总之很舒服，觉得公司虽然小但是有培养人的意识，能让我的能力得到很大的提升。自己一个人住，骑车上下班，远离市区，其实也都不错。很安静。就是路上挺烦，有一条很长的路，晚上没有灯，伸手不见五指，还有一只狗。另一条长的路特别窄，又特别多车，路又不平，提心吊胆的

OK，生物钟的问题就是早上7点半起来还是太早了，在家百无聊赖去单位又没人开门，还是晚点睡晚点起吧

]]>

written at 2008-03-04 22:09:30

2008-03-01 23:34:10

2008-10-29T08:25:00.027+08:00

3.1

从雁荡山肥来了，明天上课赶作业先，游记下次写

照片：

http://picasaweb.google.com/juvenpp/JGVfXC

]]>

written at 2008-03-01 23:34:10

2008-02-21 08:46:27

2008-10-29T08:25:00.025+08:00

2.21

昨天干完最后一班岗，收拾东西准备离开的时候，好多人来跟我道别，谢谢谢谢。很难说我到底有没有一点留恋，不过我还是得到了不少。接下去休息十二天，少少自由一下，非常之哦也

其实一年一年一年的都过的很快，只是有的时候我们发现了，有的时候我们想着别的东西没有发现。晚上看了蓝莓之夜，王家卫有点讨好观众的意思，但不影响这是部好片。我很喜欢那个阿尼，很像我，有句话一直印象很深“you are my god damn wife”，蓝莓并没有错，只是客人点了其他的。

准备过两天到上大混混，临近考试，到处都是忙忙碌碌的学生，图书馆想必早就挤满。上大那么大，我发现似乎没有一个属于我的空间了，昨天翻抽屉找出来一枚EX给我的戒指，于是想找个地方扔掉，后来总觉得这样的举动太奇怪，那么就留着吧，原来我是这么害怕寂寞的，为了填补寂寞，我的人生走上了两一条道路，而原本想要填补的，还是空空一片

准备找个地方散散心，厦门太远太贵，近的没啥意思，婺源也没到季节。。。

时间和钱的曲线同时达到峰值也挺不容易的。昨天地铁出来抬头一望，正巧赶上了月圆。今天元宵节了，但现在谁会在元宵节点着花灯走在杨柳岸边吟诗。

去年元夜时，花市灯如昼。月上柳梢头，人约黄昏后。
今年元夜时，月与灯依旧。不见去年人，泪湿春衫袖。

]]>

written at 2008-02-21 08:46:27

2008-02-07 11:50:27

2008-10-29T08:25:00.023+08:00

2.7

D语言让我激动了一把。。。

要做一个徘徊在牛A和牛C之间的人，我才刚上路呢

D语言支持功能表
这是D的能与其它语言比较的各种功能的大致快速列表. 仅限于内建于语言核心的功能. 而很多其它功能可通过标准库获得.

功能	D实现了吗
垃圾收集	Yes
函数委托	Yes
函数重载	Yes
out函数参数	Yes
嵌套函数	Yes
函数literals	Yes
动态闭包	Yes
类型安全参数	Yes
参数推迟赋值	Yes
轻便数组	Yes
可变大小数组	Yes
数组切片	Yes
数组边界检查	Yes
数组literals	Yes
关联数组	Yes
强类型定义	Yes
字符串开关	Yes
别名	Yes
面向对象	Yes
多继承	No
接口	Yes
操作符重载	Yes
模块	Yes
动态装入类	No
嵌套类	Yes
Inner(adaptor)类	Yes
Covariant返回类型	Yes
属性	Yes
内联汇编	Yes
直接访问硬件	Yes
轻便对象	Yes
明确内存分配控制	Yes
不依赖虚拟机	Yes
直接产生本地代码	Yes
类模板	Yes
函数模板	Yes
隐含函数模板实例化	Yes
部分和明确Specialization	Yes
值模板参数	Yes
模板模板参数	Yes
Variadic模板参数	Yes
混入	Yes
静态if	Yes
is表示式	Yes
typeof	Yes
foreach	Yes
隐含类型推断	Yes
契约式编程	Yes
单元测试	Yes
静态构造顺序	Yes
保证初始化	Yes
资源获得即初始化	Yes
例外处理	Yes
作用域保护	Yes
try-catch-finally	Yes
线程同步	Yes
C风格语法	Yes
枚举类型	Yes
支持所有C类型	Yes
80位浮点	Yes
复数	Yes
直接访问C	Yes
使用现有调试器	Yes
结构成员对齐控制	Yes
产生标准目标文件	Yes
unicode源文件	Yes
文档注释	Yes

什么是 D 语言?

D 是一种通用的系统和应用编程语言,它是比 C++ 更高级的语言，同时还保持了生成高效代码以及直接访问操作系统API和硬件的能力。D 很适合于编写从中等规模到那些由团队合作完成、数百万行代码规模的各种程序。D 易于学习，为编程者提供了很多便利，并且适用各种野心勃勃的编译器优化技术。

D 不是脚本语言，也不是一种解释型语言。它不需要虚拟机、宗教、或者高于一切的哲学。它是给实际的编程者使用的实际的语言，它帮助编程者快速、可靠的完成易于维护、易于理解的代码。 D 是数十年来实现多种语言编译器的经验的积累，是用那些语言构造大型工程的尝试的积累。D 从那些语言（主要是 C++ ）那里获得了灵感，并将使用经验和现实世界中的实用性来驯服它。

为什么是 D ？

确实，为什么？有谁需要另一种编程语言？
自从 C 语言被发明以来，软件工业走过了一段很长的路。许多新的概念被加入了 C++ 中，但同时维护了同 C 的向后兼容性，包括兼容了原始设计中的所有的弱点。有很多修正这些弱点的尝试，但是兼容性是最大的困扰。同时，C 和 C++ 都在不断引入新的特性。这些新特性必须被小心的加入到现有的结构中，以免重写旧的代码。最终的结果十分复杂—— C 标准将近 500 页，C++ 标准大概有 750 页！C++ 实现起来既困难又代价高昂，造成的结果就是各种实现之间都有差别，因此很难写出完全可以移植的 C++ 代码。

C++ 程序员倾向于使用语言中的孤岛来编程，也就是说，他们倾向于十分精通语言中的某个特性而避免使用其他特性。尽管代码通常在编译器之间是可移植的，但在程序员之间移植就不那么容易了。C++ 的一个长处是它支持很多根本上不同的编程风格——但从长远来看，互相重复和互相冲突的风格会给开发带来妨碍。

C++ 在标准库而不是语言核心中实现了可改变大小的数组和字符串拼接等。不在语言核心中实现这些功能造成了几种不太理想的结果。是否能把 C++ 的能力释放、重新设计并重铸到一门简单、正交并实用的语言中呢？这种语言是否能做到易于正确实现，并使编译器有能力有效地生成高度优化的代码呢？现代编译器技术已经取得了很大的进步，有些原来用作原始编译技术的补充的语言特性已经可以被忽略了（一个这样的例子是 C 语言中的‘register’关键字，一个更为微妙的例子是 C 中的宏预处理程序）。我们可以依赖现代编译器的优化技术而不是使用语言特性（如同原始的编译器所做的那样）来获得可以接受的代码质量。

]]>

written at 2008-02-07 11:50:27

2008-02-05 21:12:26

2008-10-29T08:25:00.021+08:00

跳槽了

今天上午发了年终奖，不到一个月工资，非常的谢特。。。于是乎我拿粗准备已久的辞职信，吃饭前交给老大，然后给老总，整个过程非常的紧张。。。老大还跟我谈了谈，最后我有一点点小愧疚感。不过马上要迎来新生活了，这个还是很哦也的。谢谢亿科的哥哥姐姐们～

不过以后就看不到神仙姐姐了啊，还有很多小姑娘

新工作是搞电信的，技术含量很高，用的是D语言，python,核心是C。准备在里面修炼个至少两年，再往外企走。。。。

]]>

written at 2008-02-05 21:12:26

2008-01-19 23:49:50

2008-10-29T08:25:00.019+08:00

1.19

前些天路过延长，道路比原来宽了好多，经过宿舍楼的时候又看到一直开在哪里的羊肉串铺子，在这里两年，始终都没有吃过一次，因为我们都一致的认为那是猫肉串。到大宁一路现在修成了一排餐饮店，颇有格调，想那时只有走很远的路才有的一家红辣椒。等767还是这么久，对面行健楼的等还亮着，我还能估计那盏灯下有可能有认识的人。最初的记忆是大二第一次来的时候，组成原理的一堆电线，让我又爱有很。这么快好几年都过去

“我们说好了一辈子，少了一年一个月一天一分钟一秒钟都不算一辈子”

我没办法跟任何人说这句话，想到这句话的时候我都会想念起阿毛，马上阿毛也会有新的室友新的同学，或许他会有女朋友，不知道会不会记着我，记得104，记起买西瓜的老头

“今天的西瓜很好，哈密瓜不好吃”

“我就要哈密瓜”

“西瓜很好的同学”

“我不要西瓜我要哈密瓜”

“哈密瓜卖完了...”

我们我们之间当然现在也有联系，我也知道只是内容不同了，饭桌上越来越多的股票，房子，谈婚论嫁，我怀念的可能你也在怀念，可是我们都不会提起了

]]>

written at 2008-01-19 23:49:50

2008-01-18 20:04:52

2008-10-29T08:25:00.017+08:00

快乐不守恒

人会互相妒忌，你妒忌一个人，你会失去一些快乐，这些快乐并不会转移到你妒忌的那个身上。被人羡慕被人妒忌有时候并不是很让人兴奋的一件事，每个人都有属于自己的痛苦。如果不是，我们都应该有很多的快乐。

明天又要考研了，想到去年，两天都没有好天气。我和阿毛，还有些认识的面孔。

早上考政治还遇到那个考研班上经常看到的同学校的女生，考场上感觉非常不好，虽然周围都是一个学校一个专业的，但是都觉得特别陌生。坐在第一排肖叉旁边的一个老女人，坐在最后一拍的以前总让人很不爽的机器人，周围还有很多看了让我自卑的人。总之非常难受，英语考完出来是唯一呼吸顺畅的，走出来走在上海理工两排很好看的梧桐树下面的路上的时候天色已经很暗了，几乎跟今天一样冷。树上挂着紫色的小灯。路上密密麻麻的人零零碎碎的言语我怕传进我耳中。第一晚上在家我异常的紧张，我又看了很久全书，也难掩我的紧张。最后很悲惨的一夜。。。哎

到现在很多很多很多细节我都很清楚的记得

我希望阿毛，marie，买买提，所以考研的人都能成功～

]]>

written at 2008-01-18 20:04:52

2008-01-15 08:09:52

2008-10-29T08:25:00.015+08:00

1.15

我这个人很扭捏。。。恩，有道理

肖叉不收俺。。。尊郁闷

]]>

written at 2008-01-15 08:09:52

2008-01-13 12:36:30

2008-10-29T08:25:00.013+08:00

1.13

准备开始做自己的网站

暂时是asp.net吧

噢噢噢噢

]]>

written at 2008-01-13 12:36:30

2008-01-05 17:03:05

2008-10-29T08:25:00.011+08:00

缘

Little Buddha

这两天看了两部电影，昨天晚上看了《小孤星》，简直是我自己演的。最后一直很难受，可惜豆瓣上不能打六颗星。

今天下午，这一想法再次在看完《小活佛》之后出现，或许这部给我带来的震动不是电影上的，我没办法搬来一大套电影的理论来评价这部电影。所有我想到的，大概就是一个字：缘。最后喇嘛一直念叨的form is empty ,empty is form,所有这些，出现的时机都这么完美，我感觉是佛陀在指引我。在我最迷惑的时候让我得到了这么一部电影。原来我一直对皈依有两个顾虑，一是前些天一个师兄告诉我，一切宗教都要以利益众生为任，但我究竟对世界有这么种冷漠。第二个是我觉得自己还是个禽兽，有很多很多的欲望，有些是不可避免的，肉身的。还有一些说不清楚，或许被现代人称作野心或者是雄心的一种东西，我怕皈依之后会丧失，我怕自己对一切看空之后什么都没了。但现在觉得有点开解，这两者是可以互相满足的。空也即是色，悉达多王子并没有一直苦行下去，面对他最初的追随者他说了句我前些日子悟道的话：学习就是学习改变。我记得以前见过一些出家人，他们给我的最大的感受就是他们真的很慈祥很有力量，我感到这就是佛光。

不管怎么说，给我的震动还有很多很多。如果有朋友对此有兴趣不妨看一下

]]>

written at 2008-01-05 17:03:05

2007-12-31 23:27:44

2008-10-29T08:25:00.009+08:00

12.31

最后一天

好像从来没有这么特意的留意过什么最后最初，什么纪念日什么周年。

下午几乎都在地铁上耗过去了，五光十色的四号线八号线一号线，去找昂立要报BEC高级的电影票，MM几乎给我了，最后看了看什么单子说你这是周末班，没有送电影票的，就把我手上的电影票拿回去了。。。真囧

在家看了两部法国电影，雪地里的情人，还有一部新浪潮的代表作最后一班地铁，发现法国电影真的不适合我，完全不能进入状态，本来是奔着库斯图里卡去看的雪地里的情人，没想到不是老库导演的而是他直接男主角了。。。再囧一下。看来还是意大利和德国电影适合我，下午到大自鸣钟淘到了小活佛，另外拿了《孩子》前几年金棕榈得主，还有一部日本的《沈默》我不知道为什么要拿这部，就是觉得内容介绍比较吸引我，导演都没听说过。

豆瓣上偶然看到一个回帖，关于《美国美人》的，炫耀是因为他自卑。在我身上也很能体现。昨天做了个很诡异的梦，以前有个叫杨伟的同学上课被老师点起来，很自信的说，我改名字了，改叫杨龟。。。。乱七八糟的。马上终于要过去这个年了。

fuck off。。。

]]>

written at 2007-12-31 23:27:44

2007-12-29 22:45:25

2008-10-29T08:25:00.007+08:00

我的二零零七

年末

今天终于到了年末，回家看到这个城市同时打开了三条地铁线路，一号线换乘站变得相当的壮观。可是人看上去越发的多了。每个人越来越渺小。下沉到越来越深的城市里。每一张脸带着不怎么相同的表情，有谁在意呢？我们不是天使，我们只是孩子，不怕迷失方向，在五光十色里流浪。但是，欲望很多，宁静很少。步伐很快，心情很坏。

想起

当我越来越多的写出连我自己都感动不了的日记，这迫使我去想和回忆。二零零七年的一月一号，记得很清楚很清楚，大雨的早上，闹钟没响，taxi到了密云中学听徐明德的临门一脚。花了50块钱，让100块钱的课没有泡汤，现在想想，并不是自己精打细算，而是为了给自己信心和掩饰自己的无助。二零零七年初，还在教室里坐着听课，还在食堂用饭卡买饭，还在疯狂的乞求无情的恋人的回心转意。但所有所有消失的无影无踪，这么快。连给我慢慢习惯的时间都没有。让我现在刻意回忆才能记起

麻木

噩耗来袭，如此唐突和荒谬，如果有时光机。。。这里迟疑了很久，实在有太多选择。我不知道为什么我就是哭不出来，所有的事情发生后，如同往常般的吃饭，睡觉，什么都看不出来，我对自己假装什么都没有发生，慢慢消散真的很久很久，很痛很痛。数个月后一次醉酒，还有一次和一次，我都忍不住哭出来。甚至是现在。

工作

开始的时候确实不顺利，催命的毕设，迟钝的感情反映，新的环境。一开始的几个月，我几乎不跟任何人说话，一个人在角落里吃饭，一个人上班，下班。再回学校跟一群同学狂欢，吐露心事。转机在一次偶然的机会，同事去日本出差，聊了几句，之后就越来越卸下包袱，再就是接下来的旅游，回来之后发现阳光再次照到了心里，每次路过学校，唏嘘越来越少。学校的论坛也越来越少上。不快乐的事，记得的也越来越少，我的日记，伤感越来越少。希望朋友们明白，即使我心里还有很多很多结，至少我在变得开心

前路

过去的一年，我明白让人开心的是什么。找到要做的事情。所以现在我最大的快乐，就是发现还能从学习中找到乐趣。这一年里从当当和卓越买了几百块的书，让我慢慢看慢慢读慢慢开心。二零零八年我还要读BEC高级，第一年工作合同结束之后我还有很多种选择。但是，可能有人不认同我的动力，90%的仇恨和10%的对幸福的期望。I'll show you！前几天想，其实没有什么是不能舍弃的。所以，我剪掉了很长很长的头发，从头开始2008，我看着用推子推掉的头发的时候，心里活动还是很大的。有点不舍，很多委屈，最后，默念着fuck off with the damn 2007，顶着光头离开了，冬天的风吹来，有点冷。

]]>

written at 2007-12-29 22:45:25

2007-12-29 15:28:29

2008-10-29T08:25:00.005+08:00

12.29
唐骏：社会最需要一天之内读懂一本书60%的人

从我的经历中我最清楚，我靠什么？就是靠执著。因为我的执著使我踏上日本的留学之路。日本不是我想要的地方，但是我既然来了我就学好，很多同学讲他的专业不是他想要学的，不喜欢怎么办。你知道吗？专业对你来说真的不重要，在这四年里最重要的是什么？当然我刚才说的性格很重要，但如果单从学习这个角度来说我认为学习的能力最重要。

知道现在社会上最需要什么样的人才吗？不是那种给你一本书6个月后回来你考了90分，因为这个社会变化太快了，而是一本书给你一天你回来后能告诉我书里大概60%的内容，社会上最需要的是这样的人，而这样的人在社会上一定是最容易成功的。

大学给了你这样的机会那你就应该培养这个能力，而不是把每本书读精读细那样太慢了，最好是你在一天、三天、最长一个星期你就把这本书学完了，至少掌握了60%、70%，你可以慢慢练，大一不行大二、大三、大四，大四还不行再读等等。总之，在大学里最重要的就是培养你这个能力，等到你把它学会了你踏上社会你机会一定会比别人的多得多。在这个社会我们重视工作中不断的创新和快速学习的过程。

唐骏在中南大学演讲节选

这么说来，大学里面考前一周内临时突击的那些人，其实是最厉害的人？

]]>

written at 2007-12-29 15:28:29

2007-12-25 20:49:37

2008-10-29T08:25:00.003+08:00

12.25

昨天回来的太晚，没有来得及写，只好现在补一点

“今天应该很高兴”之前就看到这句话在介绍演唱会的页面上，可惜最后当了回土著，没等他encore就走了，戆，实在是戆

跟阿K一道去的，首先谢谢阿K的票。还让她等了半天。。囧rz

内场，距离很好。等了很久很久，灯光暗下，所有人都在找明哥的身影。

没想到一出来就是满天神佛里的一个造型，不过还是很漂亮。

01.下世纪再嬉戏
　　02.春光乍洩（國語）
　　03.做一场给世界看的戏（國語）
　　04.一一
　　05.攞命舞
　　06.流浪者之歌
　　07.暗湧（國語）
　　08.一二三上海滩
　　09.不夜情
这么多国语的歌，真的很囧。他用着不怎么流畅的国语唱，下面的人用着不怎么熟悉的粤语和，有点诡异。不夜情是我很期待的一首歌，我也很肯定他会唱。“夜末有夜，上海一夜，你说烟花，只会散不会谢”

然后曝光了林夕，唱了首爱人同志，真是吃果果啊。不过他的爱人同志比罗大佑的多了些柔情，我觉得更能代表这首歌吧。接着出来了潘迪华，唱了好几首，老人家77岁了，看不出来啊，其实明哥也48了，从舞台上跑来跑去的，有点感叹岁月年华。可他还是这么妖艳，哈哈

接着曝光了张亚东

　　16.萬福瑪麗亞
　　17.你真伟大
　　18.光天化日
　　19.阿姆斯特丹
　　20.友情歲月
　　21.人山人海
　　22.今夜星光燦爛
　　23.北地胭脂+石頭記（國語）

石头记也国语。。残念啊

　　24.帶不走（國語）
　　25.菊花台（國語）
　　26.維納斯（國語）
　　
　　感謝主辦單位
　　27.我是一片云（國語）

到这里，本土著就走了。。。蟹特

另外补充一点：照相机忘了带

回到家快12点了，夜深人静的。有点意犹未尽

再补充一点，阿K也没带相机

]]>

written at 2007-12-25 20:49:37

2007-12-23 17:47:13

2008-10-29T08:25:00.001+08:00

年会

圣诞前夕，加上日本天皇生日，俺们公司浩浩荡荡二百余人在明成大酒店开了这么个年会，也是寡人第一次参加的宴会。我去的比较早，看酒店也是个四星级，竟然在一楼的厅开年会。十分的没劲。本来奔着抽奖去的，看搬上来的奖品都啥啊，乱七八糟的。总共十八桌，上菜极慢，周围人又不好意思猛吃，搞得我也不好意思。表演节目特没劲，六对男女跳舞，老板打分，前台小姐和一个日本猥琐男老板竟然打了9.9分，我靠。要引发国际口水战了。

吃的内容。。。略

然后某胖子被点到上去表演节目，什么什么新闻联播，竟然挑了神仙姐姐一起，残念啊。忘说了，平时那个神仙姐姐老是关照的猥琐男今天在所有人都穿的很随便的情况下穿了个无比无比正式的宴会装。。。阿弥陀佛

然后又是个傻逼节目。。。略

抽奖，榨汁机，床上用品，空气净化器，6，3，1.。。我靠，能不能不要这么土鳖

今天最大的一个感受就是，有小孩的人好多啊，而且很多完全看不出来啊，我还以为是小姑娘来

CMMM和神仙姐姐今天还是光彩夺目啊，还有好多好看的小姑娘啊，哈哈哈哈

]]>

written at 2007-12-23 17:47:13

2007-11-18 09:12:31

2008-10-29T08:24:00.023+08:00

11.17

今天是第一次在新blog里写字

感谢blogcn在三年里给我的回忆，幸好还有xml,让我可以自由的搬来搬去，把导出的xml文件打开，有1M多，不知道有多少字

搬家的原因似乎只有一个：这里的程序更强大。我不知道是不是现在变得理性了一些

最近看塔可夫斯基的《雕刻时光》对老塔的电影又有了一个新的认识，他的电影是诗的电影，我似乎不应该执着于镜头里的隐喻，影像带给我的是艺术给我的神经松弛，然后被她感动。本不应有什么分析之类的词语出现，就像欣赏梵高的画，自然不能把所有的像素点拿出来分析，那是科学。

又买了五张DVD，终于买到了永远的一天，DVD的画面果然又一次感动了我。

昨天看了《地下/没有天空的都市》库斯图里卡的作品，库斯图里卡现在才50多岁，希望能贡献更多的伟大的作品。

下周要旅游了，同行的人没有一个认识的，怎么办口牙

]]>

written at 2007-11-18 09:12:31

2007-10-18 12:29:00

2008-10-29T08:24:00.022+08:00

豆瓣
http://www.douban.com/collection/ilicis/movie/?sortby=rating

我在豆瓣的电影，加上脑残片满了600了

written at 2007-10-18 12:29:00

2007-10-27 08:03:00

2008-10-29T08:24:00.021+08:00

10.27
梦
早上起来做了个怪梦，我在很熟悉的小巷里看到还在读书的阿毛，黑乎乎的球衣，望着他的背影，我突然嚎啕大哭，很久没有这么舒坦
。我记得这个小巷，是我小学时候那条承载着我的童年的地方。后来阿毛不见了，我做一架很小的飞机去找他，找到之后回来，下了很大很大的雨，我同他讲生活不如意，讲毕业之后的事，讲学校，我说从前我一无所有，到了学校，我突然发现我有了很多，友情，爱情，自由，可惜这天赐终究是要收回的，我并不强求，但我非常非常的难过。这两年我过的很不好，但我还是会用我自己编造的美好的回忆安慰自己
又梦见很大很大很高的石像，还是在雨里，还有很大的骆驼，给人拍照，还是在很大的雨里
我和阿毛像打车到地铁，再坐回来，可是打不到车。偶尔看到一个，透过湿漉漉的玻璃，里面的男女正乎着热气缠绵
还遇到强卖我们芒果的小贩，占着雨水的东西，我并不想要

跌进现实
阴天，我有时候会想如果再活一次多好，有时候有想其实也没什么必要。昨天看到一句诗，自是人生长恨水长东，是我很久以前也对此沉吟许久许久的，如今看到，越发觉得时光错漏，原来着悠悠长恨，已是这般不能平息
我前些天想买个DV拍电影，可是我有太多东西不会，代价太大。我总不愿用太大的代价去做什么事情，婷姐相信我是真想拍，问我能不能把要讲的东西都拍出来，我一点都不确定，我说还可以搞女主角，堂赛过去了。
]]>

written at 2007-10-27 08:03:00

2007-11-04 22:06:00

2008-10-29T08:24:00.020+08:00

11.4
大概每到11月心情都很差
想想自己那么多仇恨那么多欲望，怎么入得了佛门呢
今天去了趟七宝，回来经过虹桥那片地方，就觉得将来一定要混到这里来
我有这种欲望，还是暂时不谈什么佛了吧，况且我不是在恨，就是暂时忘记恨
晚上日洞洞，冲啊～～

written at 2007-11-04 22:06:00

2007-11-06 22:17:00

2008-10-29T08:24:00.019+08:00

11.6

妈又给我来信了，如往常的，还是觉得我在怨恨她，如往常的，埋怨我不肯跟她多交流
怎么说呢，我只是觉得我的生活里装不下这么多东西，已经有太多东西我不想过多的去想他
但又不能完全放下，我知道将来的某个时候，我会很后悔，但我没办法
我不晓得怎么表达，即使是面对自己。
所以我想去拍电影

这些天工作忙得头晕脑胀的，想想其实这工作挺操蛋的
下班回来爸爸竟然叫我快点找个女朋友，妈的

written at 2007-11-06 22:17:00

2007-11-20 20:10:33

2008-10-29T08:24:00.018+08:00

快餐时代

下班回来的地铁，二号线，紧靠门口。对面一个算不上漂亮的女子，紧靠另一侧的门口

看她年纪大约二十四五，到陆家嘴的时候人已经挤得满满，只能窥见她半面，突然发现她开始哭，就这么含着眼泪，没有表情。我想投以安慰的目光，但怎奈生性羞涩，欲视还休了一阵子发觉自己目光颇有轻蔑之意，只好低下头去不看，然后淹没在人潮里再也找寻不到。

你也匆匆，我也匆匆，想起十七岁想起初恋，会约好去网吧，然后坐在隔着一排电脑的位置上用企鹅传达含蓄到几乎冷漠的关怀，还会在两人之间还有五米距离的时候脚步就开始慌乱，当然，是十七岁

土豆来了，标题党来了，一句话的冷笑话来了，爆笑签名来了

快餐时代

]]>

written at 2007-11-20 20:10:33

2007-11-09 22:05:00

2008-10-29T08:24:00.017+08:00

11.9

其实明天就是生日了，这些年过生日的时候总会有种不好的心情，很差很差的情绪，蔓延从十月到十一月。前几年还在宝山新校区的时候，过二十岁生日那年，我有一个月都有种强烈的预感，觉得我活不过二十岁。我小心翼翼地过马路，慢慢的走路，过生日那天，我心情极差，我不记得是不是对发现还活着很失望，总之，庆幸是没有的
今天在回家的车上打开了一个存放二十年的心结，其实这个小朋友3岁前的家庭遭遇让他幼小的心灵受到很大的伤害，以后以后很长很长的时间里他都很没有安全感，害怕一个人在家，而家人永远是忙啊忙，忙着赚钱，忙着折腾。他总是一个人在家，起初他喜欢跑出去，家人怕他走丢，把他锁在家里。他只能不停的哭，他的父母常常很晚才回来，只好哭到没力气。其实自己和自己玩一点都不好玩，最后累到睡着，发现只要睡着时间就会不知不觉地过去。他开始喜欢黑夜，把自己浸没在黑暗中，就看不到这个世界了，看到的只有自己。后来这个小朋友只好学着冷漠，学着逃避，学不会跟人交往，学不会大声说话

昨天做了个梦，我终于又决定再次考研了，那是无比无比的激动，我是如此的开心，那么的憧憬，就像又在初冬晨跑的时候闻到枯草上冰霜的味道，在太阳没有将它融化前，进入我的肺，与冷风划过我的脸一样让我感到快乐

豆瓣真好，有这么多我喜欢的小组：
人际交往障碍，孤独孩子们的集合操场，一个人的专注时光-又寂寞又美好，暧昧不起，发呆&白日梦&自言自语，自己和自己玩

叶塞尼亚，叶塞尼亚

written at 2007-11-09 22:05:00

2007-10-12 22:04:00

2008-10-29T08:24:00.016+08:00

10.12

这几天确定了一个人生目标，准备在4，50岁的时候把全部自己的财产捐掉然后出家，所以准备不结婚了，
这样到时候也没有什么牵挂
跟一些人说了，当然这些俗人肯定以为我神经病了。我是真的准备这样
我有太多痛苦，我想寻找解脱，可是我有很多欲望，我还是禽兽
现在是不能入佛门的，简单的说就是还有很多东西放不下，我到底在干什么呢，为了满足自己更大的欲望，牺牲眼前的很多很多，还是为了抛下将来的很多很多呢，
我知道我会慢慢的对很多东西觉得厌倦，然后才能抛弃
现在已经有很多我可以马上抛下的了，我厌倦国家，让人没有自由，我厌倦政治，讨厌那些整天叫嚣攻打台湾的人，很可怕。我厌倦电视，媒体，突然想起小兵张嘎这部红色电影，这个宣扬着我们不称霸的国家，如此的倡导这样扭曲人性的电影而一点都不感觉到，我突然感到很恐惧，我厌倦家庭，你们说结婚幸福，为什么我从来感觉不到，我厌倦亲情，你们整天说妈妈，妈妈，让我好嫉妒

written at 2007-10-12 22:04:00

2007-12-09 16:25:35

2008-10-29T08:24:00.015+08:00

12.07

这周末在床上躺了两天，太可怕了，从周六早上开始，看球，吃饭，看片，吃饭，睡觉，看片，吃饭，看球，而有了蓝牙，我都可以在被子里完成这些事情，看球，看片，浏览网页，看人家照片，写blog。我很担心我这样下去会不会残废掉。所以我想去报个BEC的班，然后看啊看啊就是没有双休的。

每天早上起来就TMD想到这些破事，我感觉我是被剥夺了一些权力。那好吧我用什么狗屁苦其心志自我安慰。我会变得很强大的

.net framework programe还有一周时间就啃下来了，只是学了一遍很多东西还没有动手实践过，接下来一段时间会有更多的时间用在c++ primer，习题，看代码，还有BEC

爸妈去了趟新马泰就发神经的说要把我弄到新加坡去，我一点也没有兴奋，这样的话他们还说少了吗，英国，还有那房子，鬼才会信他们的话。还是既定目标：autodesk。离现在的公司又近。他们说要把浦东的房子租掉，那你们用现金买来是干什么，让我还十年贷款。让我每个月赚来的钱一半给地铁和银行赚去了，再去掉房子的钱，每个月我能赚两百块。

]]>

written at 2007-12-09 16:25:35

2007-12-06 21:01:36

2008-10-29T08:24:00.013+08:00

12.06

昨天终于奢侈了一把，花了550大元买了个蓝牙键鼠套装，我那个心疼啊，不过回到家里用上。哎呀那感觉。。。键盘比较重，手感真没的说，就是一点缺憾上面没有状态指示灯，只能看本本上的。鼠标感觉就差了一点，个头比较大，手有点握不住，不过拿在被子里，在床单上用感觉都很不错。一点都没有无线鼠标的延迟。

昨天下午发邮件找CM要了照片，其实我是不想怎么样的，跟婷婷姐磨叽了半天他竟然说我不是男人。我后来一想决定不可以这么连跟女人说话都不敢，何况还是发邮件。我就鼓起勇气发了，用词还琢磨了半天。然后等啊等等了快一小时她回了。给我一个相册，哈哈哈

这些天突然各种各样的事情都来找我了，跟天野大魔王做的EDI，跟光原做的REM，还有每天给安部汇报的维护报告，阿弥陀佛，我还能抽空写点公用方法，明天起我准备试试能不能弄个库

二十三号公司年会，两百多人一起，不知道是什么情况。

]]>

written at 2007-12-06 21:01:36

2007-11-27 21:07:06

2008-10-29T08:24:00.011+08:00

11.27

你们有什么资格窥探我的思想？

你们有什么资格左右我的选择？

改了三年多都没有改过的副标题

]]>

written at 2007-11-27 21:07:06

2007-11-26 13:11:00

2008-10-29T08:24:00.009+08:00

11.26
水是眼波横，山是眉峰聚。欲问行人去那边？眉眼盈盈处。
才始送春归，又送君归去。若到江南赶上春，千万和春住。]]>

written at 2007-11-26 13:11:00

2007-11-25 20:03:26

2008-10-29T08:24:00.007+08:00

照片

http://picasaweb.google.com/juvenpp/JyPTs

一张张贴太麻烦了，基本是按照时间顺序

]]>

written at 2007-11-25 20:03:26

2007-11-25 19:30:11

2008-10-29T08:24:00.005+08:00

庐山游

两日游回来了，其实却是是超过我预期很多很多。有点拨云见日的感觉。原来人与人也不是这么冷漠，老总来我们房间一起看球，吃饭的时候乱开玩笑，让我感到轻松许多，完全把烦恼抛诸脑后原来是这么好的一件事。

第一日还要上班，可是没有任务，心里烦燥的很。到下班了匆匆的换了衣服吃饭，上车，上路。斜前方坐着两个长得很软的小姑娘，把包包放在我座位旁边，因为跟我不熟，所以时不时看看她的包看看我，我只自己觉得好笑，左边有跟我一样独自一人的老朱，前面也有一样的两个人，原来我也不孤单。准备上火车了认识了一个同伴。火车上旁边的人还都是自己人，玩了会牌发现自己80分还是没什么长进，识趣的让给别人了。

一路上景点很多，不都一一说了。含鄱口远观五老峰，拜访蒋介石毛泽东故居-美庐，三叠泉，第二日是白居易草堂，仙人洞，天桥，下午到南昌游了滕王阁

印象最深的一是三叠泉，台阶一个又一个，3.5KM的路一小半人坐了缆车，我走了来回7KM和一千多个台阶，走的两眼发黑两腿发颤。一路上一直有那两个长得很软的小姑娘跟着我和一个同伴，不然就没劲了。不过女人还是女人，最后吃东西去了没跟上。

然后是滕王阁，我一直对那篇滕王阁序颇敬佩，所以一直想一览滕王阁尊荣，想是何能够引人作出如此惊天地泣鬼神的作品来，上了阁可惜看到一半江水一半楼宇。

一路总能见到的那个小姑娘我都没好意思跟她搭话，却总是不经意看到她看我的目光，她从不躲闪，让我连连败下阵来。只最后出了机场，她的同伴被男朋友接去了，她一人往车站走，我上去问了句，知道什么车能上一号线吗，她指了下前面的车很小的声音回了925，我问你也坐这车吗，她说不坐。然后就再也没看到了。。。

回到上海，又有各种各样的烦心事，我也不是随便找个人填补一下空虚的年龄了。不能随心所欲了。。。以后大概也能看到她几眼，不过最可能也最好，只是些美好回忆罢了

]]>

written at 2007-11-25 19:30:11

2007-11-15 08:11:30

2008-10-29T08:24:00.003+08:00

豆瓣验证码
doubanclaim5f314d2421ceb614]]>

written at 2007-11-15 08:11:30

2007-10-18 12:28:00

2008-10-29T08:24:00.001+08:00

豆瓣验证码

doubanclaimaeeb658df1136557

written at 2007-10-18 12:28:00

2007-10-05 15:35:00

2008-10-27T21:48:00.021+08:00

《太阳照常升起》
看了这部很期待的电影，主要是对姜文前两部电影有了太多的信心。但还是在载到之前看了一些评价，争议很大，只有怀着敬意和怀疑看了遍。
首先叙事方式类似昆汀塔伦蒂诺的低俗小说，还有黑泽明的一部电影，先不论借鉴也好抄袭也好，本来昆汀之流也就是小众的代表。他们说，电影首尾相连，形成完美的圆形叙事方式，这种魔幻现实主义手法在中国电影界还是比较少见的
先理清一下思路，开头的两个故事是76年的，房祖名与疯妈的故事，黄秋生和若干个女人的故事，再回到58年，两个女人在大漠的旅途偶遇，一个为着幸福的爱情，一个为着伤心的爱情。房祖名出生
周韵疯了，自杀。黄秋生因为摸屁股冤案自杀。姜文搞林医生，。房祖名和姜文他媳妇乱搞，被姜文打死。姜文说"每一个人都不是他自己，而是社会对你的一种塑造、定义、期望，而主关的东西永远妨碍我们接近真正的客观事实，于是你也从来就无法真正知道自己是谁"。
所以电影里出现了很多超现实的主观主义的事物，南方湖边长着新疆戈壁的仙人掌，周韵离奇的草甸

在片尾和片头，疯妈重复的话"阿辽沙,别害怕,火车在上面停下来了,他一笑就天亮了"这时候太阳升起，有人说房祖名根本不存在，是周韵意外掉子后疯了的精神产物，先不讨论这种可能性，这部分有很多隐喻我暂时还没有搞清楚

片子最大的隐喻是对于性的隐喻，中间一个故事，黄秋生与几个女孩，都在压抑，姜文和林医生，林医生和黄秋生，还有摸屁股冤案，最后林医生，姜文，黄秋生三人在屋里小聚后，黄秋生上吊了。他悬挂着的自杀身躯下面，7个女人：林医生，5个厨房姑娘，1个倾慕他的骚扰女
姜文一直幻想着老婆的肚子像天鹅绒，房祖名寄托这疯妈对烈士父亲难以触及爱恨交融的强烈的复杂感情里，以致这两人在偷情的时候，一个说，你唐叔说我的肚子像天鹅绒，一个说，就叫我阿辽沙吧
所以，他们两个都实际上不是在跟对方偷情，而是跟自己幻想在偷情。

再说下另一些隐喻，电影里涉及到两个时间概念，58年（大跃进），太阳升起，房祖名出生就成了弃儿。76年（文革）姜文这个在当时习惯于讲祖国比作母亲的年代的人用了疯妈来比作什么不言而喻。
另外58-76都是中国性压抑的年代，最后，电影最大的隐喻-太阳，到底象征了什么，每个人心里都会有自己的答案吧

written at 2007-10-05 15:35:00

2007-10-05 10:33:00

2008-10-27T21:48:00.019+08:00

又来加班

这几天在家猛看电影，昨天看了布达佩斯之恋，讲那首gloomy sunday的，片子题材应该还是不错的剧本觉得有点乱，没有达到期望中的效果
太阳照常升起，非常牛B，我很喜欢黄秋生弹的那首曲子
突然想起心灵捕手的情节
我也很想有个怀抱，对我说，its not your falut,its not your falut,its not your falut,its not your falut......

written at 2007-10-05 10:33:00

2007-10-03 21:24:00

2008-10-27T21:48:00.017+08:00

10.3

这么远，那么近
上次跟他们去唱歌时候唱的这首歌
觉得是黄耀明对哥哥吃果果的告白，但是MV里是明哥和一个女人的，很失望
简直是天作之合
我怀疑，我们人生中唯一可以遇见的机会，已经错过了

十一过的真不爽，竟然被叫去加班，调休也没感觉了
还是觉得非常没意思
最近FM2008,NBA2008都快出来了，新赛季NBA也快开始了
哦后后，忘记说了上次半夜看都灵德比，好久违的感觉，一整场的打铁最后来了个高潮，哈哈哈哈哈哈

written at 2007-10-03 21:24:00

2007-10-01 22:41:00

2008-10-27T21:48:00.015+08:00

烟花烫后记
虽说良辰好景常有，烟花不常有
耳旁还是久久的响起Memory
中国场比较欢腾的感觉，美国场看似嘈杂，其实过后有种蛋蛋的忧伤
是谁那么慌
升起，消散，爆炸，平静
人们满足的退场，留下背后一片荒野
恩，
我不要拒绝像烟花一样的东西了

written at 2007-10-01 22:41:00

2007-10-01 09:45:00

2008-10-27T21:48:00.013+08:00

10.1
烟花记，感谢ZXG同学给的票，我就不要脸的屁颠屁颠的蹭过去了，带着3个MM。
烟花很精彩，可惜被一棵树挡住视线，不是很爽

一小时，再精彩也会结束的，我经常怕美好的东西不能长久，其实我不能接受结束
一个人一辈子一段感情一场经历，都会结束
现在只是过去的未来和未来的过去的一个交点
更多的时候美好只是在记忆里

工作让我忘记了很多惆怅丢弃了很多忧郁
不管他多么不好，我要努力相信这是个好的方向

written at 2007-10-01 09:45:00

2007-09-12 23:14:00

2008-10-27T21:48:00.011+08:00

9.13
这两天可以自己坐车回家，就开始想一些放了很久的事情
看到一个签名"要好好活着，因为我们会死很久很久"
我从小就很怕死，除了怕死，后来还学会了怕很多东西，这也怕那也怕的
其实人都是很没安全感的，只是我比较敏感而已
人们会用自己的发明来掩盖，就像没了手机就像失了魂一样
最近高兴的发现自己有了越来越多的可有可无的东西，QQ,手机，还有一些别的
我一个人也能过的很好
没有房子不算什么，没有钱只是暂时的

继续加息，明年月供有望超过工资了
这是个很好的跳槽理由
恩，好好活着

今天是哥哥生日，换首路过蜻蜓

若你没法为我安定
宁愿同渡流浪旅程
不怕面对这无常生命
若你没有愉快心情
来吧描述谁欠你情
黑了倦眼都侧耳倾听
让我做只路过蜻蜓
留下能被怀念过程
虚耗着我这便宜生命
让你被爱是我光荣
无论谁在嫌我煽情
不笑纳也不必扫兴
哭我为了感动谁
笑又为了碰着谁
看着你的眼
勾引我的泪
为何流入沟渠
不寄望会感动谁
只怕我会比你累
爱是你的爱
不吻我的嘴
又凭什么流泪
music
爱是我的爱
若毫无价值
为何值得流泪

written at 2007-09-12 23:14:00

2007-09-09 20:34:00

2008-10-27T21:48:00.009+08:00

9.9
九月九了，离开九九年九月九都八年了
今天去了姥姥那边亲戚家吃了饭，现在已经是小辈拿着东西孝敬长辈了，就我是空手去的，其实这里面事情还是很复杂的，算了
下午见了阿强和阿毛，商量了半天还是决定不下来吃那里，最后竟然去了burgking。。。不过跟他们在一起还是很开心的，说话还是很肆无忌惮，我问阿毛要不要做我男朋友。他竟然说不好，哈哈，他一向是这么一本正经的，很傻很可爱。阿强晚上要陪老婆了，只好就这样了。真希望阿毛这回能考上。阿强也能好好找到自己的归属。一起回忆的时候也都是心照不宣，不诉离伤。非常好。跟你们在一起总是说不够，跟我上班完全是两个人
晚上去学校给小杨一个东西，拖了好久真不好意思。现在觉得她还是不错的一个小姑娘，虽然我知道为什么最后是这样，人和人本来追求就不同。天长地久实在是一个太高的要求，还是我自己太爱幻想了。恩，很多事情都是我自己不好
原来停停姐跟我说虽然结婚自己觉得很恐怖，但听到别人结婚的一下子还是觉得很幸福的。
但是我到现在还是没觉得哪里幸福了。。。

written at 2007-09-09 20:34:00

2007-09-01 21:20:00

2008-10-27T21:48:00.007+08:00

9.1
好像牛奶不在blogcn上写字了，那我就用用她那首曲子好了
刚把我的blog从头到尾看了遍，只是想这天气合适
看着看着，看着看着，突然发现21页日记有一半都是准备考研之后写的，我突然就哭出来了

以前我都一直以为我很无辜，这些天才发现，这么些年来，我真的做错不少事情，而错已铸成，不能回头了

written at 2007-09-01 21:20:00

2007-09-01 18:58:00

2008-10-27T21:48:00.005+08:00

9.1
开学日，本该属于我的新生入学。我只能呆呆的追忆似水年华
try to remember的旋律还能一直响起
晚上想了想为什么我这么留恋，在寝室的时候我总是很早的来很晚离开，我不喜欢家里，在家也要戴上假面，在家也要搞政治，只有在学校我能有我的一点真。如今在职场，更要讲办公室政治
明天再假装学生去学校转转找人吃饭
又到冷漠清秋，我很喜欢很喜欢。。。哈哈

written at 2007-09-01 18:58:00

2007-08-28 21:26:00

2008-10-27T21:48:00.003+08:00

08-28
果然，这两天有事情做了也觉得舒服了不少。昨天老大叫我们做了个程序，今天测试好了，还没等到答复。
今天是这里成立三周年，感觉好久好久了，可惜没有记录下大一。有时候我还是会去看看以前的记录。明天又是新生报到，好多人都想起若干年前的那天。觉得也过去了好久好久了，前阵子颇为想念从前的CD，于是就冲动了一记去淘宝淘了个二手的松下CD机回来，又求购了个二手的牛X耳塞，拿出从前听过的很多碟再听。我记得旋律，记得当时的场景，可是慢慢的也记不得那时的感觉了。时间越往前，我就失去它越多。我知道这也是没办法的
我不喜欢酒吧，我喜欢在学校楼顶吹风
快开学吧，这半年还能多再学校跟以前的同学还有现在的弥留在学校的同学还有低年级的小朋友一起吃饭
在百度知道看到一个哭笑不得的问题"我是一个可爱的程序员，请问不找工作可以不"我一开始忍不住想笑，后来觉得我自己大概潜意识里也问过这个问题吧
我现在也相信一定会有来世的，去他的马克思

written at 2007-08-28 21:26:00

2007-08-24 21:20:00

2008-10-27T21:48:00.001+08:00

8.24

规则：这是圈内正流行的击鼓传花游戏，传给谁谁就得接着，否则就得挨罚。请认真对待，不要怕暴露隐

私。下面是我的回答，去掉答案就是留给你们的作业，答完后要发表在你们的页面上，且要在标题上注明

是谁点了你，你答完后加一道题再传给另外几个个人，而且要去他（她）的页面告诉他（她），不可以回

点哦～

传题人是：阿可，说阿K会跟另一个人混起来哈哈

01 要传答出去的人：一切都靠自觉吧

02 题目：击鼓传花

03 多大：22

04 职业：挨踢民工

05 兴趣:：电影、音乐、游泳

06 喜欢的异性类型：要崇拜我，内心安静，有智慧

07 专长：人品好

08 有没有什么证书：毕业生皆有的我都有，微软那个破证，上面有比尔盖茨的复印签名

09 有烦恼的事吗：无数

10 喜欢和讨厌的食物：食欲不是很强，什么都还好，什么都不坏

11 对你爱的人说一句话：你过些年再粉墨登场吧

12 介绍你要传答出去的几个人：随便吧

13 用一种动物来形容传答给你的人：猫吧

14 用喜欢的角色来比喻传答问题给你的人：怎么关于你的问题这么多，阿奴吧

15 用一种食物来形容传问题给你的人：面包

16 用颜色来形容将接棒的几个人：黑色，还不知道

17 最让你感动或激动的一件事：我凭借自己的力量考上了高中，粉碎了老师的预言和冷落

18 理想中的爱情：没有

19 如果吃好吃的第一个想到谁：没有想到谁

20 什么时候会想起传问卷给你的人：读研的幸福生活

21 最近一次哭是为什么：想事情

22最让你后悔的一件事：大四那时候认识了那个人

23 为了你最重要的东西，比如说朋友或爱人等，你能放弃什么？能放弃一切吗？

不应该有什么是在30秒之内不能放弃的

24 喜欢什么季节：冬天，很温暖

25 最喜欢的地方是：海边

26 最喜欢听的歌是哪首：王菲的所有

27 最想去的时间空间：梦回唐朝，北欧

28 如果只剩下一天的生命,会做些什么：看日记

29 如果生命可以重来,你愿意回到过去重新开始吗：想了很久，还是不愿意

30 没有面包的爱情,你会接受吗：可以

31 如果给你重新选择一次的机会,你想自己变成谁,为什么：艺术家

32 下一个被点的心情如何：题目好多

33 如果你是国家领导人,你会提出什么建议：这国家解散了吧

34 如果你有1000万,你怎么用：挥霍掉

35 你最难忘的一个人是谁：好多，不同种类都有

36 你相信爱情么：爱情是宗教吗？相信，宗教不算吧

37 你爱的人背叛了你,你会怎么对他(她)(两个人正面对着)：无视

38 怎么样的朋友可以做一辈子的朋友：志趣相投就OK了

39 亲情友情爱情当中最看中的是：爱情

40 你认为家庭是爱情的阻力吗：是

41 什么才是你最想要的生活：其实什么都差不多

42 你觉得什么时候的月亮比较好看：满月

43 如果50年之后我们擦肩而过你还会认识我吗, 是在水里还是陆地上：海上吧，自己有游艇

44 给你一个神灯,你现在最想要许的3个愿望是什么：

NO 1 pass

NO 2 pass

NO 3 那就世界和平吧

45 王子喜欢公主多一点还是灰姑娘多一点呢,为什么：公主吧，贫贱出身得到富贵之后性格一般会比较怪

46 认识我,你的感慨：你是个很不错的小姑娘哈哈，我一点都不妒忌你，你应该得到的

47 你会为了自己的爱情,和父母反目吗：可能会

48 1加1等于几啊：2

50 最想的职业是什么：艺术家

51张柏芝为什么看上小谢了：地球是圆的

52 现在最想谁：没有特别在想的人

53 写完这个有什么感想：做了好久

54 最喜欢什么颜色？为什么：黑色，纯粹

55 最喜欢的睡觉方式：趴着

56 什么时候才能见到你：说谁呢

57 如果让你知道谁发明的这个击鼓传花游戏，你会如何问候ta？你很好，很强大

58 如果你实在没有办法和最爱的人结婚，你会选择独身一辈子吗？如果不是，你会选择你爱的人还是爱

你的人？：我爱的人吧

59 你觉得自己今后的伴侣会是怎样情况下结识的呢？别人介绍的吧。。。我比较没出息

60（我的问题）：你觉得到底有没有来世？别笑，我最近想了很久这个问题

看到的都要做，不认识我就算了，看到了假装没看到的，我不认识你

written at 2007-08-24 21:20:00

2007-08-24 10:30:00

2008-10-27T21:47:00.038+08:00

8.24
本来是无甚可写，不过发现了马桶这个小面板的功能。可以收文章来看就好了。
最近发现我突然能想出很多可以开发的软件，但就是技术不到位。从下个月开始要潜心研究技术了。其实我还是很想经常去去上大，可以一起吃饭的人还是不少的。最近在公司里好久都没事干了，闲得我很恐慌。况且来了个新人，有点点压力。其实没有暑假也就没有了，以前或者现在看别人都是期盼开学的多。昨天入了一个MX90，价格还是很和谐的，这样一下子就到动圈比较高的档次也不用烧来烧去了，动铁不动铁以后有钱了再说。
前几天跟停停姐吃了个饭，原来这饭好简朴啊哈哈有点过意不去，本来她说人均200我想想那要花掉我400大元啊一下就穷了。。。
昨天又跟个小姑娘说了半天尤文，我怎么会说这么多呢想不通，我这人就是这样的谁说我喜欢的东西我就会发疯的，谁都不能说尤文不好，绝对不行。十三年的忠贞不二，这就是"当爱已成习惯"吧。。哈哈

vivian问我去过汤姆熊没有
我说没去过。。。

written at 2007-08-24 10:30:00

2007-08-18 17:35:00

2008-10-27T21:47:00.037+08:00

8.18
有一阵子没来写，上次打完仙剑过来码了一篇一保存没了，余怒渐消，于是再过来写写
今天还是去了6613聚会，感觉吃的一般，聊也没啥聊的，人太多，桌子太大，关键的一些东西好像都忘了说。
这都不是关键
重点是，再次之后，我就不打算再出现了
BEC学是要学的，考不考看情况而定。另外还要学.net和c++，还有余就看php
就是闭关了，什么时候出关，还是不设期限的好

written at 2007-08-18 17:35:00

2007-08-01 15:30:00

2008-10-27T21:47:00.036+08:00

8.1
我很不开心，突然很怀疑自己，从好久以前就开始没有干好一件事，高中想考交大，进了大学想插班，想考研，等等。我不知道会不会接下来的一个目标还是像这样。最近看了几个小朋友的blog，有些跟我那时候很像，不过我也很羡慕，会用哭来渲泄，而我对痛苦和幸福都反应很慢。痛去如抽丝，半年来我一直难以释怀，每天早上都会痛苦的发现原来这些都不是梦。

written at 2007-08-01 15:30:00

2007-07-29 21:51:00

2008-10-27T21:47:00.035+08:00

7.29
大概后天就能买到仙剑4了，作为一个仙剑迷的回报，我这次就买正版了。前几天买了两本砖头花了80多块，不过还好有点盈余
晚点有尤文对纽卡斯尔的比赛，我要好好看看，其实十三年来，每次当黑白色的球衣在出场仪式上出现，我就无比的激动，到现在都没变过，镜头一个个球员照过来，我心里都会默念他们的名字
明天又要上班了。。。慢慢习惯这种节奏吧
天热，没啥好写的
还有一个月就开博三周年了，目前来看有望到10000访问
又想想开始2004年，想起来我为什么要开这个blog

恩，还是到9月开始我才闭关，我来试试断网几个月的味道

written at 2007-07-29 21:51:00

2007-07-26 22:29:00

2008-10-27T21:47:00.033+08:00

7.25
其实工作上并不十分愉快，一定的其实周围的人都很少说话
我想说话但是回家以后就没什么心情了，夜里总是想很多很多东西，等到第二天睡觉前再记下来，就记不起来了
手机每天似乎也只有几个特定的时间才会看他一眼还好今天快递把我的书给我了，好大两块转头
好好读书，好好学习
今天老总主动跟我打了个招呼，把我惊了一讶，貌似同事对他评价一般。每天看到他都是中午吃盒饭，下班挤地铁
跟停停姐说觉得很没劲，我是真的觉得很没劲，麻烦能不能不要来烦我
下个月初阿超就要来上海了，好多时候没见，挺想
还是怀念武汉的同学
前两天跟那个小妹妹说起上海她说不喜欢这个冷漠的城市，其实很多年前我也会把这句话挂在嘴边的可是现在也说不出，疲惫的在混乱中眩晕，纸醉金迷，就是这样的感觉
到最后人的娱乐是什么呢？男人的娱乐是女人，女人的娱乐是钱
我很不喜欢那种一进入职场就把自己的学生味完全漂掉的人，错气死了
你们就说我不成熟好了，你们去成熟去
更不喜欢那种在学校里也要把自己搞的很职业的，看了两张她后来的照片，难道你就不觉得你的眼里灵魂是很苍白的吗

written at 2007-07-26 22:29:00

2007-07-24 22:30:00

2008-10-27T21:47:00.031+08:00

碎碎念（开始与结束之间）
这不是开始，也不是结束
今天看到李国正网页里的研究生信息，又觉得恨，悔，念一起袭来

昨天晚上睡觉时候突然就想跟阿毛阿强去唱歌，我在上海的朋友其实一点都不多，就他们，加上CXY也算是吧，跟他认识不久，但是觉得很相投
就是很想点那首逝去日子，不知不觉世故已学懂

written at 2007-07-24 22:30:00

2007-07-20 20:00:00

2008-10-27T21:47:00.029+08:00

7.20
今天拿到了职业生涯第一份合同，一年期，钱不多，但是我的起步，我的菜鸟合同正式开始了
工作上还是有点点小小的不爽的，不过我会努力克服。
天气热就是很不想写很多。。。晚上睡觉才有空调
昨天睡觉前想一个问题，到底快乐的人和痛苦的人，谁才拥有智慧？痛苦的人心里充满矛盾，而矛盾就是智慧的代价。后来我想通了，其实真正越过这个障碍达到豁达而快乐的又有几个，而大凡这些，也是经历了重重矛盾与挣扎才拨云见日的，芸芸众生中看似快乐的人其实只不过是无知而已

written at 2007-07-20 20:00:00

2007-07-16 11:27:00

2008-10-27T21:47:00.027+08:00

7.16
上班没事干真是很奇怪的一件事，今天日本那边不上班，俺们也没什么事情，同事好多都没来。明明觉得上班有事情比较忙还是不错的
blogcn也开始ajax一把了。。。
最近准备又想看.net framework程序设计了。。。总是计划大于行动
没劲啊没劲啊
快点过些时候闭关了吧
其实每天都心情很差的，想到那个房子，想到这些恶心的人。。。我都不敢想像还有多少年要每天看到他们

written at 2007-07-16 11:27:00

2007-07-15 07:57:00

2008-10-27T21:47:00.025+08:00

7.15
好吧说下上周五，工作第一次出了点问题，前一天有点问题没解决好就走了仕黑这个仅次于天野的人估计很不爽，然后第二天我出了点问题他就发飙了，搞的我最后加了一个半小时的班，其实加班很爽啊又有钱拿又没什么事情干，我爱加班我爱加班
其实是我喜欢一个人在那里，没什么人管，我也喜欢一个人坐班车回家，没人管我
堂哥从美国回来了，什么时候去瞧瞧
干IT的其实在上海4，5年达到10K/M的也很多，但是5K的也很多，这是前天从CSDN上了解的，我总是不明白为什么每个人都要高薪每个人都要做经理那哪有这么多程序员，其实到了工作才知道，每个人目标真的不一样，每个人的现实也不一样，每个人的能力也不一样。生活很无奈，当你有了老婆，有了孩子，一切都不同了
所以说，一个人的时候是很宝贵的，要好好抓紧这几年变的强大

written at 2007-07-15 07:57:00

2007-07-13 08:23:00

2008-10-27T21:47:00.023+08:00

给新人程序员的八点建议

走过弯路，有过迷茫，回首九年陈皓感慨万千。"今天，我对许多刚上路的朋友都会说，人生的规则很重要，从上大学时就要好好规划。"他结合自身经历，对许多刚踏入程序员行列的新人程序员，他给出了以下八点建议：

1. 在大学的时候尽量多地进入公司参与实际工作，一方面积累工作经验，另一方面，提前认识工作和自己，以便毕业时更准确地把握自己的方向。

2. 从毕业开始到毕业后至少5年内，踏踏实实地专研技术，这是一个积累过程，千万不要把心思放在钱和职位上。钱和职位只是能力的附属品，不要让其喧宾夺主。

3. 从毕业后3年到7年的时间，注意学习工作当中的方法以及相关的管理和流程，不但要知其然，还要知其所以然。

4. 30岁以前，踏踏实实地学习。学技术，学做人，学做事。30岁以后再谈自己的发展。

5. 毕业后的前5年主要是量的积累，要不停地积累知识和方法。毕业后的5到10年主要是质变，应该着重于思维和想法的更新。后五年应该有很强的包容能力和接受新东西的能力，千万不要太过固执和坚持自己的想法。

6. 换工作要"承前启后"，前面的工作会成为后面工作的一个基础，而后面的工作又会成为前面工作的一个很自然的延续。

7. 不要只把心思放在技术上，技术是hard skill，只要下工夫就一定会掌握。更要注意与人沟通等为人处事的soft skill上。hard skill像一个大树的根，而soft skill则像一个大树的枝叶。树根是你的根基，能让你站得很稳，而枝叶能让你向天空伸展，获得发展。

8. 对于程序员来说，应该始终记住，技术不是主要的，主要的是通过技术能够解决什么样的问题。一定经常想要解决什么的问题，要满足什么样的需求，而不是要用什么样的技术。

原文地址：http://news.csdn.net/n/20070710/106274.html

written at 2007-07-13 08:23:00

2007-07-09 21:16:00

2008-10-27T21:47:00.021+08:00

7.9
最近觉得什么都很匆匆忙忙的，没心思静下来想，其实好久都是这样了，开始有点点讨厌坐地铁，很烦。以前说的生活的意义在于找到自己该干的事情，现在我就要好好学C++和英语，每天就这件事情比较开心吧，其他的都不那么好。
发现自己还是那样，容不得别人说我喜欢的东西不好。。。
烦

written at 2007-07-09 21:16:00

2007-07-09 21:37:00

2008-10-27T21:47:00.019+08:00

7.9
那一场风花雪夜的事
我有时候像是看到了另一个自己，离开我的身躯，越走越远，或者说是我坐在火车上，看着留在某个地方的另一个我，越走越远，回头望，风景越看越美，远山，长河，落日，孤雁，我不明白如何年纪轻轻平添了这样多的沧桑感。我喜欢看到广袤的风景，虽然这样我显得渺小。我感觉不到身边的幸福，就算是你给我落下一场花瓣雨，我总会错过的。太美丽的东西总要离开一段距离才能消化和体会
花瓣雨，飘落在身后

我怕走的太快来不及踏雪寻梅，来不及琴心剑胆，来不及来不及

上次看电影体会到一点，有句台词说自从有了电影，人的生命延长了三倍，因为电影有人生不能经历的，但是生活丰富的时候人又总觉得过的特别快，所以最终还是没有什么不同。只是体会的方式而已
你要细水长流还是激流勇进？
还是头脑清楚点，是生活方式选择我而不是我选择生活方式

written at 2007-07-09 21:37:00