最近程序写得有点累，就像妈妈原来常说的，“一个人收拾，一堆人霍霍”。
Patch programmer几乎从来不做refactoring，只做外部可见的事情，几乎从来不删除代码，他们所做的工作就是在代码上打补丁，或者在补丁上打补丁。更糟糕的是，他们会选择最省事的方式，比如将private改成public，或者其它简单粗暴的方式打破人家辛辛苦苦设计的封装。他们根本闻不出代码的smell，不理解人家为什么摆一个如此复杂的架势去完成一个“简单”的功能。所以，他们就“化繁为简”，打破重重阻挠，取出最核心的东西，然后将整个程序耦合在一起。
辛苦倒也罢了，可是这样下去不是浪费生命吗？！换工作的心都有了:-(。刚刚读了fear of code，不知说什么好，一声叹息吧，唉！
O’Reilly Network: Ruby on Rails: An Interview with David Heinemeier Hansson:
“That’s not necessarily an easy sell, though. Just see all the wars through the times over coding standards. If people could just agree on one way of placing their brackets, they could presumably reap more readable and uniform code. But for a lot of people, that didn’t work because the trade wasn’t appealing enough. Getting a more uniform code base is frequently not treated as importantly as individual ‘freedom’ by a lot of programmers.
Rails essentially tries to do the same as the coding standards did, but the reason it’s working better is that the deal is much sweeter. Getting a uniform code base is an abstract, group-centered goal. Seeing your application work in a fraction of the time it took you before is a very concrete, individually rewarding goal.”
netcasper：始终搞不清coding standard是指什么？有时似乎是指使用某种编程语言的注意事项，也有时是指代码的格式。上文应该是指后者，其实如果是前者的话还是会受到欢迎的。
