why is ‘testing’ after ‘function definition’ in the design recipe?

actually why is it even after header/why is header before examples?

i.e. i’d think that tests can help you nail down what exactly the function consumes/produces, and i bet most ppl are thinking of examples while writing the purpose statement


i’ve never actually taken a class that followed HtDP, what i learned/do is closer to red-green-refactor where starting with failing test(s) is important. i especially like this for DSLs/DSDs because your goal is usability in addition to correctness

Sign in to participate in the conversation

A Mastodon instance for programming language theorists and mathematicians. Or just anyone who wants to hang out.