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

让非程序员明白我在说什么。

通过实现客户想要的东西来满足客户——不幸的是，这意味着客户知道他想要什么。

通过学习一门精确的科学，我不需要提高我有限的社交技能。

因为性能问题，像Java和。net这样的虚拟机架构对于除了玩具项目之外的任何东西都毫无价值。

(好吧，公平地说，也许在某些时候这是真的。)

我仍然对以下的一些误解感到困扰——尽管我知道这些误解是正确的，但我仍然试图抓住它们不放:

All stakeholders will make decisions about software design objectively. Those that aren't embroiled in writing the code make all sorts of decisions based entirely on emotion that don't always make sense to us developers. Project budgets always make sense - I've seen companies that are quite happy to drop [just for example] $50,000 a month for years rather than pay $250,000 to have a project completed in 6 months. The government for one loses their annual budget if they don't spend it - so spend it they will, come hell or high water. It astounds me at how many project dollars are wasted on things like this. You should always use the right tools for the right job - sometimes this decision is not in your hands. Sometimes it comes down from on high that "thou shalt use X technology" for this project, leaving you thinking "WTF! Who came up with that ridiculous idea?"... the guy paying your paycheque, that's who, now get it done. Programming ideology comes first and foremost, everything else is secondary. In reality, deadlines and business objectives need to be met in order to get your paycheque. Sometimes you make the worst decisions because you just don't have time to do it the right way... just as sometimes that word is on the tip of your tongue but the minute it takes to recall it makes you choose a different and less ideal word. There isn't always time to do it right, sometimes there is only time to do it - however that may be. Hence oft' seen anti-patterns used by so called experienced developers who have to knock out a solution to a problem 10 minutes before the presentation deadline for the software being delivered to your best client tomorrow.