Re: Any interesting philosophy of programming articles to recommend?

Some items off the cuff:

Design Patterns in Dynamic Programming - a presentation by Peter Norvig on how Design Patterns are a way for OO languages to cope with missing abstraction capabilities
Alistair Cockburn's papers on methodology
I don't know if you have access to this, but in the ACM digital library there are all the articles of Jon Bentley's famous "Programming Pearls" column, including the (out of print and therefore "lost") articles that are collected in "More Programming Pearls". Old, but still worth reading to me.

Update: There is a new book out that should be very interesting reading: "Software Fundamentals. Collected Papers by David L. Parnas". A recommendation in the ACM journal compared it to "The Mythical Man Month" in terms of importance.

Christian Lemburg
Brainbench MVP for Perl
http://www.brainbench.com

Comment on Re: Any interesting philosophy of programming articles to recommend?

Replies are listed 'Best First'.
Re (tilly) 2: Any interesting philosophy of programming articles to recommend? by tilly (Archbishop) on Aug 20, 2001 at 18:26 UTC
Judging from the first two, I will enjoy Alistair Cockburn's papers. It will take me a while to get through that. :-) I should also note that on my home node there are quite a few random links. People who are looking through the various links in this thread might also like to follow some of them. And a random exercise for the brave that just came up in chatter. Keep a log of bugs you discover in your own code, with notes about what you think caused the bug. Review that log periodically. If you feel truly brave, have someone you respect review said log with you. Excellent, if painful, way to learn what you personally need work on.	[reply]

Replies are listed 'Best First'.

Re (tilly) 2: Any interesting philosophy of programming articles to recommend?
by tilly (Archbishop) on Aug 20, 2001 at 18:26 UTC

I should also note that on my home node there are quite a few random links. People who are looking through the various links in this thread might also like to follow some of them.

And a random exercise for the brave that just came up in chatter. Keep a log of bugs you discover in your own code, with notes about what you think caused the bug. Review that log periodically. If you feel truly brave, have someone you respect review said log with you. Excellent, if painful, way to learn what you personally need work on.

[reply]