这种简单性几乎总能战胜复杂性。愚蠢的规则。

编辑:正如葛格所说，我把这个颠倒了。我的思绪一定是在回复中迷失了。如果使用得当，简单性几乎总是能让代码变得更好。

所有面向对象语言都有相同的面向对象概念。

Java接口=方法的接口。 Java接口是针对需要具有多重继承的特定于语言的解决方案。Ruby的mixin尝试解决同样的问题。 Javascript中提供的开箱即用的继承与Java实现继承的方式非常不同。

我一直认为，任何为任何语言编写任何代码的人都会使用编辑程序。

I was working with a client of mine who had me on mostly as support and to write some of the more complex things for him. Well one day he messed up a file, big time. He accidentally saved over three hours worth of his own work, and when I asked him why he didn't save more often he replied with, "because I wasn't done". Naturally, this was not an acceptable answer, and I poked and prodded a little further. I eventually came to find out that he he has never used any editing program, EVER! Not even notepad.exe! He had been using an online CPanel editor for files! It didn't even have a 'Find' function. He couldn't ever save until he was done because he was editing the live file on the site!

不用说，我很惊讶，他至今仍在使用CPanel编辑器……

软件的质量会带来更大的销量。有时确实如此，但并非总是如此。

我认为我应该尽可能地进行抽象。我的脑袋被这个撞了，因为太多交织在一起的小功能。

现在我试着让事情尽可能的简单和分离。重构使事物抽象比预测需要如何抽象要容易得多。

因此，我从开发规则它们的框架转移到完成工作的功能片段。从来没有回头，除了当我想起那段时间，我天真地认为我会是那个开发下一个大东西的人。

假设我把代码写得很好，尽可能没有错误，这就是我能做的最好的事情。事实证明，有时候经理们更喜欢那些努力成为他们最喜欢的人，而不是把工作做好的人。