Information Technology Dark Side

Struggles of a Self-Taught Coder

Information Technology Dark Side header image 2

Collegiality by James Bach and Observations on Rigor of Waterfall by Chris Chapman

December 3rd, 2007 · 1 Comment

About a year ago Mike Kelly and I got into a bit of an argument about something, and he ended up blogging about it. It was one of those experiences that either makes a colleague a friend or an enemy, and fortunatlely it worked out in a way that has been great for both of us. I often think about that moment when I am hesitant to give another person negative feedback because of the tremendous value that resulted from that crucial conversation. It usually gives me the encouragement I need to try, even if it seems like jumping into a briar patch.

This morning I noticed a similar post by James Bach about a blog war he got involved in with a blogger named Jim Pensyl, aka Jake Brake. I thought the way their conflict was resolved was refreshing and encouraging – it reinforced my belief that IT people who are not afraid to engage in honest, skilled dialog can make a difference. Check James’s post out – it is worth reading.

Here is a part that struck me as particularly insightful:


Collegiality is much needed in our industry. And I’m not talking about mere politeness or live-and-let-live passive rivalry. I’m talking about people who do the hard work of creating connections with each other that allow for differences while also constructively questioning differences. This is a matter of chemistry, sometimes. There are people whom I have been completely unable to connect with, despite my best efforts. It’s also a matter of motivation, because best efforts take a lot of energy.

Here’s the rest of the post.

Chris Chapman, a consultant out of Canada, noticed my post on The Rigor of Waterfall. He posted an outstanding critique of my article that expanded my understanding of the issue. I’m sure he would appreciate any comments you might have to add to the discussion. Here’s a quote I particularly enjoyed:

While I do enjoy reading about another developer’s Conversion on the Way to Damascus, David’s piece stands out to me because outside of Craig Larman, he’s the only person I’ve come across who makes reference of Winston W. Royce’s role in the story of the waterfall model. While Royce isn’t really responsible for the waterfall model – that came about as a result of our industry’s 30 year failure to RTFM – knowing who he is and the history behind phased delivery is vitally important to putting the rationale for agile/lean/iterative models into their proper context.

You can read the rest of Chris’s post here.

Finally, DJ1.0 sent me a link to an article from Joel Spolsky that I think is eminently useful – How to Demo Software.

If you enjoyed this post, make sure you subscribe to my RSS feed!
Stumble it!

Tags: Agile

1 response so far ↓

Leave a Comment