我正在对初级(也许是高级)软件工程师所犯的常见错误和错误假设进行一些研究。
你坚持时间最长、最终被纠正的假设是什么?
例如，我误解了整数的大小不是标准的，而是取决于语言和目标。说起来有点尴尬，但事实就是这样。
坦率地说;你有什么坚定的信念?你大概坚持了多长时间?它可以是关于一种算法、一种语言、一个编程概念、测试，或者任何关于编程、编程语言或计算机科学的东西。
当前回答
Python是一种不切实际的、令人讨厌的语言(我仍然可以读到一些关于我早期代码的注释，抱怨它)，而c++是唯一真正的面向对象语言。
我错得太离谱了，到现在还觉得羞愧。
其他回答
当主流设计模式在计算机科学课上被引入时，我认为它们很棒。在此之前，我有8年的编程经验，对于如何创建好的抽象概念，我真的没有扎实的理解。
设计模式就像魔法一样;你可以做一些很棒的事情。后来我发现了函数式编程(通过Mozart/Oz、OCaml、后来的Scala、Haskell和Clojure)，然后我明白了许多模式只是样板，或者额外的复杂性，因为语言表达能力不够。
当然，几乎总是有某种模式，但它们在表达性语言中处于更高的层次。现在我一直在用Java进行一些专业编码，当我不得不使用访问者或命令模式等惯例而不是模式匹配和更高阶函数时，我真的感到很痛苦。
在开始开发之前，您可以完全理解问题。
My co-workers were/are producing supposedly bad code because they sucked/suck. It took me a while to learn that I should first check what really happened. Most of the times, bad code was caused by lack of management, customers who didn't want to check what they really wanted and started changing their minds like there's no tomorrow, or other circunstances out of anyone's control, like economic crysis. Customers demand "for yesterday" features because they are stupid: Not really. It's about communication. If someone tells them it everything can really be done in 1 week, guess what? they'll want it in 1 week. "Never change code that works". This is not a good thing IMO. You obviously don't have to change what's really working. However, if you never change a piece of code because it's supposedly working and it's too complex to change, you may end up finding out that code isn't really doing what it's supposed to do. Eg: I've seen a sales commission calculation software doing wrong calculations for two years because nobody wanted to maintain the software. Nobody at sales knew about it. The formula was so complex they didn't really know how to check the numbers.
标识列不能包含重复值: Sql server中的identity列
所有面向对象语言都有相同的面向对象概念。
Java接口=方法的接口。 Java接口是针对需要具有多重继承的特定于语言的解决方案。Ruby的mixin尝试解决同样的问题。 Javascript中提供的开箱即用的继承与Java实现继承的方式非常不同。
