Saturday, March 6, 2010

Will the open-source community *ever* get it's collective @$$ together?

Seriously. There are some absolutely brilliant people out there, and I learn a metric $hit ton every day from their efforts - seriously. (As opposed to an imperial $hit ton!) One thing that drives me absolutely friggin' nuts is the cyclic-incompatibilities (remember dll hell? Now try it with source-code!), conflicting source-control systems, abandoned projects abound (Code-Plex no longer being updated, now using or svn or google-code or...) and no communication ("apparently") among the elite, mutual-admiration societies.

It's actually does more harm than good for the Open Source Community. Most C[x]O's have no idea how much open-source is actually being leveraged in active projects. If it is really the way to move software forward - then it HAS to provide a better mechanism than what it is trying to replace.

I love open-source, and I contribute in any capacity I can - whether I use it, or not. I've wasted more personal hours than I care to remember, tracking down some incompatibilty because the "published" source is no longer updated - or is the "wrong one". Struggle with one project - to bring it's references up-to-date, only to find another dies "horribly" in it's wake.

I actively challenge those that I admire; how exactly is that giving to the community? How is that being a responsible thought-leader?

I think it would be fan-friggin-tabulous if they practiced what is preached and built code against each other's source as opposed to abandoned (read "obsolete") binaries, included - or better yet NOT included with their accompianed source.

Why would I have to carry "x" different versions of Castle around to see if project "y" could be leveraged into my domain problem of the hour? What the f*%k is the deal with NHibernate? and every Open Source project leveraging some version - or another, from 1.X - 3.x - and everything in-between?

I think it's only fair, because we poor-slobs coming in behind you - often finding the obscure and usually catastrophic bugs have enough to do working for "the-man". We appreciate the efforts and can certainly lend a hand - we have to do it anyway, but you have to work with those of us in the trenches!

Questions, comments, brick-bats?

More Cowbell

Exactly what the world needs - more Cowbell! Spruce up anything in MP3 format - magically, I tend to go heavy on the Christopher Walken option myself.

Make your own at MoreCowbell.dj

Wednesday, March 3, 2010

Rube Goldberg

For those of you young enough not to know who Rube Goldberg is, wikipedia to the rescue! As developers, we constantly have to integrate with systems in a variety of ways - sometimes not the most efficient. The allure of the gag is its over-complexity to perform a simple task. This can probably be best described as an anti-pattern - but none-the-less, is interesting to watch. Thanks again, to the "treadmill guys!"

Ok GO

Friday, February 26, 2010

Top 3 Visual Studio 2008 Pet Peeves

Stupid. Stupid Stupid. Annoyances. There are more...but if 2010 carries any of these over, there WILL be hell to pay!

Number 3 (Visual Studio is busy)
Busy, Really? Sorry I was only working!

I particularly like the "Hide" box that I captured by accident.

Number 2 (Visual Studio decided to restart)
No, not yet wait!

I love this one ALMOST as much as the automatic WU reboot feature.

The Number 1 (The Cylon-feature; or ain't running those tests)
The Cylon Feature!

We should all be writing unit-tests, right? TFS test integration sucks - I coined this "feature" Cylon. It's one big dumb eye swaying back (a.k.a. - the indeterminate statusbar) Once it gets into this state NEVER comes back - without a hard start of the IDE or a prompt task manger kill of the test process host.

Yes, everyday! Many, many, many times over!

Oh damn it! The IDE's gone cylon again!


Yup. That's what it feels like

Update:
Just came across an even better collection - and I thought Studio hated ME best!
http://blog.eveningcreek.com/?page_id=193

Monday, February 22, 2010

I am the laziest blogger

But its only because I'm too interested in everything else. Stumbled upon DevLabs which is a great set of resources! As well as CLinq which promises to ruin, yet another one of my weekends.

Tuesday, July 28, 2009

That's a great idea! Too bad it's doomed for failure.

An informative article, highlighting the "Brilliant, yet doomed" technologies that came and burned-out. I must be getting old, if only because I remember (better than I'd like to) a majority of these - certainly not the Babbage-machine, I'm not Methusala!
Sometimes the best horse doesn't win the race.