Using Interfaces to Abstract your Modules

I'm an old fart living on the bleeding edge of technology. Started off as a EE out of college and got into embedded programming back in the 80's for a while and then did my share of PC programming starting in the DOS days all the way up to using the latest stuff in .NET 4.0. I've been programming on and off for about 25 years now and continue to love figuring out problems and seeing things work and understanding the root causes for why we solve the same problems every year. Did my fair share of PM'ing and Management over the years, but mostly stick with programming because frankly, marketing people scare the heck out of me (much like clowns do).

I'm a huge advocate for solving systematic development problems with improved processes as opposed to re-factoring and/or throwing new technology at a problem and hoping for the best because some inexperienced kid tells us it's awesome. I'm the "old guy" who knows best because I've done everything a crap load of times using every new method out there and so I do know best.

My sincere hope is that some day our industry will stop re-inventing the same "wheels" in order to make a short sighted buck, and move towards a model of true innovation where software transcends the current fixed patterns we re-implement each and every day in an endless cycle. Is there life out there among the drones?

I enjoy fishing, camping, SCI-FI MMO's, Aquariums, shooting lizards with a BB-Gun and of course, eating food so spicy that it strips the lining off your colon.