tag:blogger.com,1999:blog-4887447608343482497.post6177480679461732414..comments2008-10-14T13:26:32.729-07:00Brandon Bloomnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4887447608343482497.post-9979272662581979392008-10-14T13:26:00.000-07:002008-10-14T13:26:00.000-07:00It definitely is a form of test driven development; good call. <BR/><BR/>However, I think the key difference is that real tests need to compile and run. Imaginary APIs can exist in an email or document and never actually need to be compiled. But yes, the next step from here is unit tests :-)Brandon Bloomhttp://www.blogger.com/profile/16981101182779460140noreply@blogger.comtag:blogger.com,1999:blog-4887447608343482497.post-27947283222506746662008-10-14T13:20:00.000-07:002008-10-14T13:20:00.000-07:00I think you might be able to consider "imaginary APIs" as a type of test driven development.<BR/><BR/>No matter what you call it, I think it's a good way to start developing a clean API.<BR/><BR/>(On a random note, the captcha for this comment is 'ggsux'. Is Google self bashing now?)dfj225http://www.blogger.com/profile/11861386349413591562noreply@blogger.com