tag:blogger.com,1999:blog-9099907.post7021474937039381986..comments2021-10-26T20:42:19.297-07:00Comments on Rebecca's Blog: What Drives Design?Rebecca Wirfs-Brockhttp://www.blogger.com/profile/02844092142697047388noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-9099907.post-15540064312859403332009-07-29T14:10:22.204-07:002009-07-29T14:10:22.204-07:00Domain model as a glossary, sequence diagrams as r...Domain model as a glossary, sequence diagrams as roadmaps and TDD as "completely verifyable specification" are the driving forces in my projects. CRC cards help a lot when clustering domain model elements and creating sequence diagrams. Thanks for the articles and the book "object design".Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-9099907.post-59170314784795034382009-02-21T11:35:00.000-08:002009-02-21T11:35:00.000-08:00Requirements keep changing.Good design ensures cha...Requirements keep changing.Good design ensures changes get accommodated well. I have never seen "Good requirements". They are always incomplete. (And that's why we exist, Software Engineers :))Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-9099907.post-67172397617080856922009-02-17T07:07:00.000-08:002009-02-17T07:07:00.000-08:00Rebecca,I enjoyed your article because I see TDD a...Rebecca,<BR/><BR/>I enjoyed your article because I see TDD as a form of writing "executable specifications", and I can confirm that design takes place in conversations before writing the next test ... ahem ... executable specification.<BR/><BR/>Cheers, MatthiasAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-9099907.post-87296772971963419242009-02-13T16:12:00.000-08:002009-02-13T16:12:00.000-08:00Alsor-I like that characterization, too. But one f...Alsor-<BR/>I like that characterization, too. But one fervent TDDer I know very well who attended OOPSLA thought I was putting down TDD by that phrase. I had no such intent. It really is a matter of if you were to looking for where people were "designing" when they practice TDD, it would be in the conversations they had with their colleague before they wrote the next test.<BR/><BR/>I think that there are different rhythms for design and that sketching out a general idea or using CRC cards to model a bit before starting to code also fits into an agile frame of mind. Especially when something is new and uncharted.<BR/><BR/>Cheers,<BR/>RebeccaRebecca Wirfs-Brockhttps://www.blogger.com/profile/02844092142697047388noreply@blogger.comtag:blogger.com,1999:blog-9099907.post-43898327580032361252009-01-30T14:42:00.000-08:002009-01-30T14:42:00.000-08:00I like the words from one of your slides: design b...I like the words from one of your slides: <B>design between the keystrokes</B>. I'd like to print out and put them near to my screen, so that they being always hold in mind.<BR/><BR/>I really "feel" the values of TDD. Especially the aggressive approach of writing tests - you write your test as it easy to be written and just that points you to the right direction for design decisions about you code.<BR/><BR/>If someone ask me about which interface should be there or how I spread responsibilities between classes, I always say that only test (first) can show.<BR/><BR/>I totally agree that requirements is not what drives you design. It's not a tool for making decisions. All programmers always have requirements when they're writing code, but not all of them do it great.alsorrrhttps://www.blogger.com/profile/05011575252347909221noreply@blogger.com