Software: Roller Coasters and Tire-Swings

Disclaimer: Okay, the music stuff is pretty slim these days (me being unemployed and all), but the geek stuff is in full effect. For you non-geeks out there... sorry. You can read up on my personal/family stuff over on the Hot Tub, but old Hickory Wind will be a tad bit more technical here on out -- mostly music and computer geekery.

Anyway, I've been thinking a lot about software design and development lately. A lot! I've been trying to figure out why it's so difficult, why most software ends up sucking, and what I can do to change it. Also, since I'm still unemployed, I've been in some interviews where I'm trying to explain to employers what I can do to fix all this.

Basically it boils down to this -- communication. Getting the requirements, understanding the requirements, being able to semi-accurately predict how much resources it will cost -- time, money, technologies, number of developers, support cost, the whole shindig -- this is what I do. And to be honest... I'm much better than most, but I'm still learning. Our industry is still so new... I mean it's only been around for about fifty years. It's an infant industry!

Anyway, I'm sure to elaborate more in the future. I just wanted to set the stage for future geek rants/ponderances, so be ready.

What tipped this off today? Well, Ben sent me this picture again today. I saw it a while ago, but it's still so relevant.

So, Mr. or Ms. Employer, let me assure you what my talent is.... I hear the customer describe a three-rung swing, realize they want a tire-swing, convince them they want a tire-swing, design a tire-swing, work with the programmers to build a tire-swing, ensure the tire-swing is safe and fun, and then help you, Mr. or Ms. Employer, convice the customer to pay for the roller coaster. That's correct. I recommend you hire me at your earliest convenience.