Why should you read this blog anyway?

I’ve been where you are. I have what you want.

Maybe you’ve read some OOP pattern books or heard some furtive whispers in the hallway about this whole rumored ‘doing things the right way’ thing. Or perhaps whilst Googling MSDN docs, you’ve happened upon suspiciously clever A-lister .Net blogs where oh-so-clever Californians or Canadians are constantly talking about their “NHibernate” or their fancy pants “mock objects” for “Unit Testing” or using a bunch of “curly quotes” all the time. Just exactly, what the hell is going on?

Where do these people work? Where do they get the time to do these things? Let’s face it, your boss is all about pushing out code, not you faffing about trying some sort of pie-in-the-sky best practices. How are you going to tap into these alt-coder / hacker / tron / war games / the matrix patterns when you are in a beige cubicle next to the emo graphics guy or maybe the Dell laser printer if you are lucky? What exactly is this stuff all about, and will you look cool if you start doing it?

The answer is of course, in this blog.

Here you’ll find:

• sensationally adequate code snippets
• tools for automating quotidian developer tasks
• the wisdom of my innumerable failures
• masonic-like secrets as to which of the patterns, frameworks, and hyphenated-buzzword-phrases are worth sneaking in when no one is looking

The bottom line:

Some tools, practices, frameworks, and patterns are geekily complicated and not worth pursuing outside of code-nerd one-upsmanship. Others however, are powerful time savers and will add to your subgenius slack and metrosexual code-slinging cred. This blog is your little black book for scoring some dead sexy development, instead of churning out the usual ‘great-personality’ variety that has your friends talking behind your back.