我正在对初级(也许是高级)软件工程师所犯的常见错误和错误假设进行一些研究。
你坚持时间最长、最终被纠正的假设是什么?
例如，我误解了整数的大小不是标准的，而是取决于语言和目标。说起来有点尴尬，但事实就是这样。
坦率地说;你有什么坚定的信念?你大概坚持了多长时间?它可以是关于一种算法、一种语言、一个编程概念、测试，或者任何关于编程、编程语言或计算机科学的东西。
当前回答
总有一天，我会有一个现实的想法，那就是构建一些重要的代码/系统/什么的需要多长时间。
其他回答
一个WTF总是一个糟糕专业的证据。
事实上，我最近才意识到在我的职业生涯中有多少WTF，但当StackOverflow告诉我它们只是另一个软件指标时，我感到欣慰。
创建一个成功的应用程序只需要程序员就可以轻松完成。软件也要易于使用，美观，文档和适当的营销。软件开发是多学科的，如果一门学科不及格，应用程序也可能会失败。
以为我是唯一一个会写代码的人……然后当我需要这个例程时，我不记得我做了什么，只是复制/粘贴我自己的代码。
我知道每个人都这么做。
通过学习一门精确的科学，我不需要提高我有限的社交技能。
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.
