Here’s a complete PhD thesis paper on the software engineering analogy [pdf] (a little different from the construction analogy).
Tag Archives: software architecture
Archive Journal Entry: 20030326
My friend Charlie has started a blog. He suggested that I start adding some photos to my own, specifically my avocado project. Unfortunately I have some technical difficulties (not enough usb ports on my laptop) so I cannot upload the photos right now.
More news about my Software Construction Analogy paper: there is another article on kuro5hin.org, this one about software architecture. It refers to my article. I have also participated substantially in the discussion there. I’m hoping that in a few weeks I will be able to publish a more scholarly attack on the software construction analogy. Eventually, I would like to develop the ideas into a full book. How many words are in a standard technical book? Addison Wesley, one of my favorite publishers, has some guidelines for book submissions.
Today was a crumby day. I had a very bad headache that started last night and continued until this evening. It seems to be gone now, but I didn’t make it into work. I have an important deadline coming next week so that was very frustrating. Tomorrow I have a morning meeting with the CIO of the organization I am working with – I hope I feel much better!!!
Archive Journal Entry: 20030314
Yesterday I submitted an abridged version of my paper “The Software Construction Analogy is Broken” to Kuro5hin. It was submitted at 9:30 pm EST, and posted to the front page of Kuro5hin at around 11:00am EST today. Someone by the name of Hamis Harvey has already written some very intelligent comments on my article on his blog. The larger paper itself deals with the same topic but provides a substantial set of scholarly references and notes as well as some differences in the text. The paper is not yet complete and I am grateful for the many excellent comments people have made on Kuro5hin. I intend to honor those comments by making my paper even better (and of course acknowledging the sources of the improvements!). Thanks K5!