tag:blogger.com,1999:blog-4254062391982392824.post1514357228804286405..comments2023-03-16T22:22:13.652+13:00Comments on Designing Code: Pretending to have written codeKeithhttp://www.blogger.com/profile/08109858095787759082noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-4254062391982392824.post-24092281609715426612006-12-16T05:24:00.000+13:002006-12-16T05:24:00.000+13:00Keith,
In my opinion you are correct and right on...Keith,<br /><br />In my opinion you are correct and right on target.<br /><br />I have been doing "Design by Use" for many years. It is applicable at some many levels. At an inner-function, inner-module, or inner-class level it is very effective. While you are designing your solution you write the code as if the underlying code already exists. It is definitely a type of top down design. Test Driven Development also derives its design power by doing the same thing. Another aspect of Design by Use (DBU) is that it is applicable at high levels. Teams can write code as if functionality already exists, functionality that will be created by another team. I explain that dimension of DBU in a web paper:<br /><br />http://home.att.net/~geoffrey.slinker/maverick/DBU.html<br /><br />Excellent observations and advice, thanks again Keith.<br /><br />Geoff Slinker<br />http://digerati-illuminatus.blogspot.com/Geoff Slinkerhttps://www.blogger.com/profile/12365501393247949005noreply@blogger.com