Magic Strings - they're bad right? What are these repulsive warts on good design? And why do they want to melt my code? The fear of strings drives otherwise talented and wise developers to do some extraordinarily ridiculous things...
I was incredibly skeptical when I heard about WebMatrix. I was dismissive and snotty about the WebMatrix data access story. I called the WebMatrix IDE a "MySpace Code Editor". I was wrong. They got it right, and I'm really impressed.
A judge from Microsoft's .NET County submitted a 00110101 year restraining order on Friday against Microsoft's C-Sharp development community. The stay-away order bans Microsoft developers from using the compiler's services as a development tool, forcing them to find other means to support their claims they "they are done" with features they are developing.
An idiom that I really like in Ruby is the ability to use a Hash to send arguments to a method. It's not something you would expect - the method calls tend to be quite verbose, yet they are incredibly clear and concise. In VB (back in the day) - passing arguments in an Array was considered a good thing. In C# 4.0, we finally have the flexibility to do this properly.
I’m never shy about my opinion – why start now? I’ve been reading a lot of posts flying about on whether you should learn MVC, Summing up the differences so you can decide when to use it, I even found a post that offers a scorecard approach!
Props on this one go to Scott Hanselman who pulled me back from the edge of the cliff last night. I was particularly distraught in getting a MIX demo together where I had to do some queries using LINQ, and I couldn't for the life of me figure out how to fashion an IN query!