I agree that the principles, practices, qualities, wisdom about good software are not confined to OO technologies (I've seen design patterns used in Fortran, and my friend Amir Kolsky once taught a TDD course in COBOL). However, they are easist to see/discuss/outline in OO, because OO sprang from them.
Here's a link to a talk I did about the subject:
http://www.netobjectives.com/resources/books/emergent-design
(click on the link "Watch Scott's webinar about Emergent Design (1 hour)"
It's a multi-media (camtasia) recording, so be a little patient if your bandwidth is limited.
Slashdot Mirror
I agree that the principles, practices, qualities, wisdom about good software are not confined to OO technologies (I've seen design patterns used in Fortran, and my friend Amir Kolsky once taught a TDD course in COBOL). However, they are easist to see/discuss/outline in OO, because OO sprang from them. Here's a link to a talk I did about the subject: http://www.netobjectives.com/resources/books/emergent-design (click on the link "Watch Scott's webinar about Emergent Design (1 hour)" It's a multi-media (camtasia) recording, so be a little patient if your bandwidth is limited.