LINKBLOG for April 1, 2008

• Book review: C# 3.0 in a Nutshell - Jon Skeet
  


• What's Wrong With This Code (#19) - K. Scott Allen
  Cool code sample showing multiple flaws on different levels


• Did you know... You can display Guidelines in the Editor, and Tip of the Day ends today - #184 - Sara Ford
  


• Optimal Debug Settings for VS.NET 2008 - D. P. Bullington
  


• The Evolution of Status Pattern - Steven Smith
  On how easy new requirement follows new requirement getting you into trouble if you start with a simple initial design


• Lessons from 4 independent years - Scott Berkun
  Thinking about going solo (and 75% of us seem to dream about this every once in a while - undocumented statistic I saw somewhere the other day) read Scott's advice


• Visual Studio 2008 Tips: Implement Interface Regions and Organize Usings Settings - David Hayden
  It's these small tips that make code monkey life a little bit more bearable


• Let That Be a Lesson To You, Son: Never Upgrade - Jeff Atwood
  ' Apparently, Linux is so complex that even a world class software engineer can't always get it to work '


• Using aliases for better code readability - Jeremy Jarrell
  Good tip!


• Blame Canada - Kyle Baley
  Couldn't resist linking to an ALT.NET related post, especially since this one carries an interesting revelation - unless Kyle is playing an April Fool's Day joke, that is :-) Guess we'll never find out who's really behind it


• Pursefight owner revealed... - Igloo Coder
  More revelations. ahh.. and more and even more, and a compilation.
  Stop the madness people, you very well know that is was me, not you, after all!
  


• How to: Optimize the memory usage with strings - Dot Net Facts
  


• WPF Disciples in 3D - WPF Disciples
  new blog, will have to see how this one evolves. Topic will be clear from the title


• Success Oriented Architecture - Payton Byrd
  Payton tells you how your architecture can be a success instead of a failure


• *** PTOM: The Dependency Inversion Principle - Jim Bogard
  Very clear description on how you could refactor your highly coupled code. If it's not directly obvious I advice you to just copy/paste the code and changes to see how it is done


• What Do YOU Do With an Overloaded RSS Reader? - Robert Hruzek
  Funny post via Chip Camden


• Setting up authentication in asp.net MVC - Justin Etheredge
  


• Fast Priority Queue Implementation of Dijkstra Shortest Path Algorithm - Tolga Birdal
  


• Towards Bug-Free Code - Patrick Smacchia
  Ways to improve the quality of your code


• Faster string building - Andre van der Colff
  Implementation of a StringBuilder, which, while being not so fast as StringBuilder itself, doesn't have the memory issues that the latter one can end up with


• Reflector Add-in Starter Kit (C#) - Jason haley
  If you don't have a use for Reflector add-in templates, you could still pick up the idea of using custom Visual Studio templates to prevent heavy cut-and-past actions for all your new projects


• Printing on Paper - Don’t Do It, Man! - Alvin Ashcraft
  Idea is nice, but I still like to do my longer read from the dead-tree version of the Kindle... or maybe I'm a cheapskate not willing to pay the $400 for a reader


• Two Kinds of Knowledge - Steven Smith
  Wonderful geeky explanation
  ' The second kind of knowledge consists of things you've stored "by reference" in your brain ' Give it a read if you're also constantly scouring the internets for the code you need: there is still hope for you :-)