Blogging will be lighter over the next week as I’ll be on the road — family vacation (at least for me and the kids) in Colorado near Rocky Mountain National Park, then on to Dallas for a talk, hosted by the Society of Information Management.
In the meantime, I’m going to queue up the next Code Reads — one that I have not yet read, so it’ll be new to me as perhaps to some of you: Daniel Berry’s The Inevitable Pain of Software Development, Including of Extreme Programming, Caused by Requirements Volatility. Thanks to Will Sargent for the suggestion.
It’s now about a year that we’ve been doing this series and I’ve completed 12 installments, so the appropriate thing to do is to stop fighting the inevitable and accept that this is a monthly schedule! What I will try to do is keep that monthliness honest. So this paper will be the October edition. That should give me plenty of time…
There are no revisions for this post.
What a great read. Among other things, I learned what the context was for Parnas’ and Clements’ paper on “Faking It”. Love learning more about the classics.
The Belady-Lehman graph was new to me, even after reading and re-reading Code Complete, the Mythical Man-Month, and Facts and Fallacies. Is it too much of a simplification to say that the upswing portion of that graph is an inevitable result of the conflict between the essential and accidental complexity of software, or at least the pain of dealing with the accidental complexity, especially of delaying dealing with the accidental complexity?
Lots to chew on here. Thanks, Scott, for posting it (and hosting these discussions), and to Will for suggesting this article.
Daniel, glad you like it.
Scott, I don’t know if Code Reads encompasses interviews as well, but there’s an interview with David Parnas which is fascinating:
We could do interviews — this thing is whatever we want it to be.
From what I can see that page is just a short excerpt from this much longer Parnas interview. I’ll have a look when I get a chance…