Process Over Technology

As the struggles continue with the application rewrite I'm currently involved with, I've read and reread these articles by Joel Spolsky, James Shore, and Chad Fowler on why this path generally leads to failure. After I finish reading articles like these I often ask myself: since many of the industry thought leaders think these projects are a bad idea, why are they still so common? I mean, Joel's article was written in 2000. Eight years later (an eternity in technology) that article is still extremely relevant, but it's lesson has failed to penetrate mainstream thought.

There's not enough industry focus on how best to approach legacy system enhancements. Many software development articles that garner the most attention focus on quality improvements delivered through innovations in technology - new programming languages, frameworks, APIs, architectures, and hardware. While that stuff's definitely important, they're relatively little help to application developers looking to extend the life of existing systems.

Martin Fowler's Refactoring book is the best example I've read for extending the life of existing software. This book - and articles like those in the opening paragraph - are timeless because they describe thought patterns for maintaining applications. Their lessons are applicable regardless of any specific technology or language.

In a recent StackOverflow podcast Joel Spolsky and Jeff Atwood discuss a recommended reading list for developers (Jeff had a previous post on the subject). In looking through their lists, I'm not seeing any "Teach Yourself Perl in 8 Hours" or "Ruby for Dummies". Specific technology is not the focus here. These recommendations teach software professionals how to think - improving quality, efficiently, and allowing them to deliver greater value.

I'm starting to believe that there are an increasing number of developers who are starting to think more like this (or at least I'm meeting more of them) - focused on improving processes rather than relying on technology innovations for increased software quality. I hope this mindset spreads to more of the development teams I'm working with.... before the next big rewrite. This thing is painful.

*****

Jeff Atwood also had a recent post on Dealing With Bad Apples. He has a similar take to my Observations in Poor Management.

Comments

Dharmesh said…
Exceptionally thoughtful article.

I think the reason we don't see more focus on the "get more out of what you have" is related to "agency syndrome".

Extracting more out of legacy systems is not "fun" and in a pure economic sense, is not valuable (for the individuals making the decisions). If I didn't own the company (or have a significant stake), it'd be hard to invest the energy into getting more out of legacy systems. That's why so few people do it.
July 21, 2008 at 7:16 PM
Post a Comment

Popular posts from this blog

I Believe...

A recent reorg at my company left me with a new manager - and a different approach to software development than my team had been previously following.  Our new approach is one that I don’t necessarily agree with, but it led me to think about - and reevaluate -  those tenets of software development that I think are important and that I believe lead to increased quality and productivity. This post will consist of fairly high level discussions about how to organize code, teams, and projects - but contain very little actual code. Many of these ideas will not be my own.  They are mostly ideas I’ve learned from others and their willingness to share their experiences with me.  They are, however, ideas that I’ve practiced and hardened as I’ve worked to build my own ideal environment for delivering value through software . Many of these ideas I now take for granted as commonplace (even though they aren’t).  I felt a need to document them anyway - so people can unde...
Read more

More stuff to get excited about

Chrome OS I'm excited about Google's announcement to release what sounds like an ultra lightweight OS to basically surf the Internet. I'm hoping this device will allow me (and others) to breathe new life into old, underpowered laptops, allowing them to essentially work as netbooks. This could also open up new and inexpensive opportunities for schools to recycle or prolong the life of expensive computing equipment and expand horizons of their students. I've been watching the One Laptop per Child (OLPC) movement for some time and I see this as another avenue toward their goal. I don't share the optimism that this OS will somehow replace Windows. Sometimes you need extra horsepower and functionality. I edit a lot of photos and create some simple video, but the web tools I've tried to do either task can't hold a candle to the four-year-old version of Photoshop Elements I own. I'm not sure CPU intensive apps like this will port very well to the web....
Read more

A few quick notes

It's been a quiet few months. I haven't worked on too many things I've felt like writing about. That's not to say I haven't been busy. One thing I've been reading more about building great teams and delivering more to our customers. I'm just starting to read Creating Magic: 10 Common Sense Leadership Strategies from a Life at Disney . Obvious from the title, this book outlines the approach Disney teaches all of it's Cast Members (employees) on how to be great leaders and provide their visitors with great experiences. I've been wanting to read this for some time and I'll be sure to write more as I work my way through it. Some related blog posts I've enjoyed recently are: The Duct Tape Programmer from Joel on Software where he reviews a chapter of the book Coders at Work . The post basically talks about doing the simplest thing possible to get something out the door and into people's hands. Amen to that! I've also been enjoyi...
Read more