Not comprehensive by any means. Here’s some blogs I enjoy from People Not Named Scott Hanselman:

• General C# knowledge – http://wesnerm.blogs.com/net_undocumented/
• ORM and general MSFT gossip – http://weblogs.asp.net/fbouma/default.aspx
• Clemens Vasters site on communications, IoT, etc – http://staff.newtelligence.net/clemensv/
• Roy Osherove’s site – http://artofunittesting.com/

What I’m reading now:

An interesting article here on Technical Disobedience – and how one team lead started out a project with a plain vanilla build out with click-once deploy to QA/PROD – as a starting point – and after Azure/Amazon EC2 got shot down – used a local machine to get builds set up. I also enjoyed the story on how they progressed from TFS to a whiteboard… and ended up phasing out TFS! (If its simple and it works, you can’t improve on it.)

From this site I also enjoyed a simple definition of survival mode (putting out fires vs learning the skills to stop starting the fires to begin with!) – and a list of fixes (starting with 1-5x increase in time estimates). The team leader manifesto makes for a good read. And I’ve read and enjoyed many of the books he recommends here. Of course Robert Martin’s book is the standard.

Async and Await patterns (SalesForce used this extensively along with dynamic objects in their new .NET library) are excellent for anything long-running (read – files or image uploads, multiple web requests, WCF programming) – a great starting article is here. I tend to use async actions by default in setting up new controllers; it’s almost as easy as writing a synchronous method (just use async and await keywords, silly!) and greatly improves the responsiveness of a UI.

This is an older article here from ScottGu on ListView – and it’s .NET 3.5 – but I found it helpful in solving a problem recently with a form at work.

And on a personal note, I liked this article on self-publishing (using leanpub, Amazon, CreateSpace, and marketing. $11,000 in profit over two months is not too shabby. I really do want to write that book someday.

What an interesting article here. POCO heresy – “Code first O/R mapping is actually rather silly“!!! and this one on Microsoft losing traction/trust in developer land: “trustworthiness is closely tied to how much responsibility you want to take for the lifecycle of your product…. Microsoft blew this on several fronts and on several occasions in the .NET world.”