我最近才发现在Hello World中执行了超过一百万条指令!我写的c++程序。我从来没有对像一条cout语句这样简单的东西有过如此高的期望

我很早就开始学习编程了。那时我14岁左右。我有各种疯狂的想法，但不要问我准确的时间，因为那是很久以前的事了。

Ok, so, I believed for a while that if you use the term synchronize in Java, then Java solves this nasting synchronizing thing for you I believed for at least half a year, likely more, that static typing would improve performance. I believed that freeing something would return memory back to the OS. I believed that malloc calls boil down to checking if there is enough free space on the OS, so malloc would be inexpensive. I thought a long while that Java was built with all the benefits and flaws of the other languages in mind, into a "perfect blend" that would take the best properties of the other languages and reject the mistakes. I vastly overestimated the number of cases where LinkedLists outperform ArrayLists. I thought that NP-hardness was a proof that no INSTANCE could be solved efficiently, which is trivially false, for a while. I thought that finding the best flight-plan on travel agency web sites would take so long because of the "Travelling Salesman Problem", as I proudly chuckled to my relatives (when I was small, alright?!)

还能想出更多。不知道我坚持了多久。对不起。

PS: 啊，好吧，这个被清除得并不慢，但我看到新手时不时地这样做，所以我想你可能会感兴趣:我还认为要存储不确定数量的东西，你需要为每个东西声明一个新变量。所以我要创建变量a1 a2 a3…，而不是使用一个变量a，我将它声明为一个向量。

在很长一段时间里(大约5年)，我认为PHP很棒。

我以为我懂算法。然后我加入了Topcoder.com

Java将对象的副本传递给函数，而不是引用。

换句话说，我认为如果你将一个对象传递给一个方法，然后以某种方式改变对象，它不会改变调用范围内的对象。我总是将对象传递给方法，操作它们，然后返回它们!

我知道要编写一个合适的web应用程序，当我必须设计在所有浏览器上都能运行的东西时，我很清楚这一点。

事实证明，在Linux下是否检查内存分配是否返回一个引用并不重要，因为它实际上会欺骗你，在未来的某个时候实际分配内存，或者如果它没有你需要的内存，就完全终止你的程序。