Thursday, October 12, 2006
On the Reading Table
Read three interesting articles in a week. That's not bad. The first was "A Study of Design Characteristics in Evolving Software Using Stability as a Criterion", in IEEE Transactions on Software Engineering, May 2006 (yes, I'm behind sometimes).
A study of software that has been in use, and has significantly evolved for three decades. What is still the same, and what has changed? The example has some Fortran specific bits in it, but this was a pretty interesting and unique article.
Then we had Componentization: The Visitor Example. By our own Bertrand Meyer and Mrs Bezault.
A really bad article was "Designing for Recovery". Can people please, please read OOSC2 and what Eiffel's view on exception handling is? This article was absolutely confusing because of the absence of clear definitions.
And did you know that Knuth's volume four has been published? Found out why this has been kept secret in "The Atrocity Archives" by Charles Stross.
A study of software that has been in use, and has significantly evolved for three decades. What is still the same, and what has changed? The example has some Fortran specific bits in it, but this was a pretty interesting and unique article.
Then we had Componentization: The Visitor Example. By our own Bertrand Meyer and Mrs Bezault.
A really bad article was "Designing for Recovery". Can people please, please read OOSC2 and what Eiffel's view on exception handling is? This article was absolutely confusing because of the absence of clear definitions.
And did you know that Knuth's volume four has been published? Found out why this has been kept secret in "The Atrocity Archives" by Charles Stross.
posted by Berend de Boer @ 20:24 
