LINKBLOG for December 19, 2007

• Pursefight round-up for 18 December - Alt.Net Pursefight
  Another new blog in town. This one picks the cherries from the alt.net mailing list which, as I think Oren said, currently has about 200 messages a day. Who wants to keep track of that? Well, as there's 200 msgs. a day there must be *some* people with enough time. Anyway, to find the (slightly opiniated, of course) cherries it seems enough to keep track of that little blog.


• Twenty excuses to avoid learning - Tim Stall
  


• How to use Custom Assemblies with Reports - Gerhard Stephan
  Gerhard shows how even the simplest code change can have you looking for hours why it's not working


• A state aware generic list - Mads Kristensen
  Very slick and maddeningly simple idea to have a List that keeps track of it's own state


• Nobody Cares What Your Code Looks Like - Jeff Atwood
  ' nobody cares what your code looks like. Except for us programmers '


• CLSCompliant is Still Off By Default - Dave Donaldson
  ' I'm willing to bet that most developers assume they *are* writing CLSCompliant .NET code when in fact they aren't '


• Checklists - Adam Barr
  ' Telling someone to make their design as simple as possible isn't helpful--unless the developer never even thought about simplicity (...) '


• Scott Hanselman's Computer Zen - Moq: Linq, Lambdas and Predicates applied to Mock Objects
  ' (...) Moq, which may be the coolest derivative open source project name ever '


• Are you handling all your exceptions? - Maurice de Beijer
  ' In Java there is a rule that every function must either catch or declare every possible exception (...) In the .NET world there is no such requirement and the result is that it is a lot harder to see what kind of exceptions might be thrown '


• Tell MS about your Team Foundation Server - Grant Holliday
  So they can learn from your TFS configuaration.


• How uTest will destroy your Quality Assurance - ISerializable - Roy Osherove
  Seems to be some new way of testing: put your new app on the web and let random surfers test it
  ' Can you imagine a company doing the same anonymous type of outsourcing to its development process? Oh wait, this happens too'


• 8 Simple Rules for Designing Threaded Applications - Ajay Mungara
  An important one, avoiding race conditions
  ' You need to be able to recognize those times when it is absolutely necessary and implement some form of synchronization to coordinate the execution order of threads relative to each other '