From the back row: "Gee, that's sad. Blogs come and go, get over it man!"
True enough, but... I couldn't help make a loose connection between this and a fairly hot topic raised on DNR - Is software development too complex? back in November. It spawned a huge series of follow ups and comments (both for and against). But it's hard to argue that the number of CLI languages, data access choices, logging frameworks, etc, etc (ad infinitum) are reducing. When you start a new project, which one to do you choose? Which one is "right"? Which one will still be a good choice in 2 years? In 2 minutes?
Q: There's a huge amount of choice out there, and it's constantly increasing! What are we to do?
A: (That guy from the back row is still here) "Get over it man!"
This is a great time for .NET development. The platform is mature, popular and stable. The huge variety of technologies available within that platform are a sign of this. Sure you will pick technological dead-ends, or the next-shiny-thing will seem so much better. But perhaps this helps focus the effort on design - being able to back out of dead-ends, or support switching to the next-shiny-thing.
I just hope the (seemingly) overwhelming choice is not driving talented people (like Arjan) away from the .NET platform. I honestly don't think so - but for a brief moment the connection was made in my addled mind.
Maybe a fitting salute to Arjan's contributions is to select some of the gems (there's plenty more):
- It Doesn’t Matter If You Know What You’re Doing
Doesn't matter who you are, or what you are doing, or even if you (think you) did it well. A review will always help... - FACEBOOK'S MEMCACHED MULTIGET HOLE: MORE MACHINES != MORE CAPACITY
Don't you wish you had that sort of problem. Adding the 801st server makes things worse... - Spec Explorer: A Model-Based Testing toolKind of "research QA team" crowd, but an interesting way to try and solve state-explosion...
- Website Background Services Are HotGetting your webserver to do something else it was not designed to do (but still needs to do). Personally I prefer Jeff Atwood's cache depndency version, but I'm easily swayed by the next-shiny-thing...
- Writing an SVN PreCommit Hook in .NET that integrates with Jira
Very simple example of how to integrate the hooks and avoid some of the pain with SharpSVN. - The passionate developer: I do like my profession, I don't like my jobPassionate about something you know is imperfect. Those zany developers, what were they thinking...
Dammit! - Now I've started a link-blog!