您无法诊断生产中的“间歇性错误”。重新启动服务器是解决这个问题的唯一方法。

也许在我早期的ASP编码中更真实。但是有很多很好的分析工具可以发现内存泄漏和其他奇怪的问题。Perfmon还提供了许多良好的诊断数据。另外，您应该在应用程序中编写诊断日志。

我最大的先入之见是，我将被允许以我想要的方式编程。当然，后来我离开了大学，进入了一家拥有荒谬框架、规则和程序的公司，这不仅意味着我不能以自己想要的方式编程，而且意味着我编程得很糟糕。

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

我相信创建程序就像在课堂上教的一样……你和一群人坐在一起，讨论一个问题，想出一个解决方案，等等。相反，现实世界是“这是我的问题，我需要解决它，开始”，十分钟后你又遇到了另一个问题，让你没有真正的时间来有效地计划解决方案。

我曾经认为我是一个很好的程序员。在那个职位上干了两年。

当你在真空中工作时，很容易把房间填满:-D

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

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.