如果你看不懂我的代码，那你就是不懂这门语言。我有一些代码审查，我试图反击。

我又花了几年的时间才明白，有一个时间和地点可以让你的代码变得神奇，那就是在库中，而不是在应用程序中。该应用程序是为了清晰和可读性。Magic最好隐藏在扩展方法和框架后面。

总有一天，我会有一个现实的想法，那就是构建一些重要的代码/系统/什么的需要多长时间。

作为一名老的过程式程序员，当我第一次开始为一个业余项目用Java编程时，我并不真正理解OO。编写了大量的代码，却没有真正理解接口的意义，试图通过将所有东西都强制放到继承层次结构中来最大化代码重用——当一个层次结构无法容纳清理时，希望Java具有多重继承。我的代码成功了，但我现在对早期的东西感到畏缩。

When I started reading about dynamic languages and trying to figure out a good one to learn, reading about Python's significant whitespace turned me off - I was convinced that I would hate that. But when I eventually learned Python, it became something I really like. We generally make the effort in whatever language to have consistent indent levels, but get nothing for it in return (other than the visual readability). In Python, I found that I wasn't doing any more effort than I had before with regard to indent levels, and Python handled what I'd been having to use braces or whatever for in other languages. It makes Python feel cleaner to me now.

640K应该足够任何人(DOS)。多年来，很多人都相信这一点。

当我第一次拥有8MB内存的系统时，我认为这远远超过了我的需求。它可以运行操作系统(Mac)以及我使用的所有应用程序(Word、Email、Firefox等)。

我写的所有东西在可预见的未来都会失败。

并不是说一切最终都不会崩溃，而是在我的编程教育早期，当我发现try. catch块…我把所有的东西都包在里面....有些事情，如果失败了，将代表比我的程序处理的更大的问题(例如，北极和南极互换了位置)。

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

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.