If you’ve ever been debugging a managed app, only to be unable to evaluate any of the locals or parameters because the code was “optimized”, check out the article below. It shows a quick trick to disable optimizations by way of a .ini file. This is great because it doesn’t force you to recompile the application and takes only seconds to implement.

Reading another Jtenos’ blog, I came across this article about things Hollywood thinks can be done with computers. Humorous read.

If only people spent as much time writing comments as they did speaking to the evils of comments. Everything from useless, inaccurate, to many comments make code unreadable, you should code better … etc.

Recently I had to test a class which heavily depended upon a SynchronizationContext. This threw me off for about half an hour as I didn’t want to write multi-threaded unit tests. Multi-threaded code is difficult enough without adding needless threads.

If you haven’t come across this post yet about inlining changes in 3.5 SP1 it’s a good read. The short version is, value types will have better performance.