>On the prototype pattern: >... >..what? Then why did you bring it up at all? From the intro: "Prototyping — slapping together code that’s just barely function

>On the prototype pattern: >... >..what? Then why did you bring it up at all? From the intro: "Prototyping — slapping together code that’s just barely functional enough to answer a design question — is a perfectly legitimate programming practice. There is a very large caveat, though. If you write throwaway code, you must ensure you’re able to throw it away." Prototyping — coding without architecture in mind? I dont find it relevant to his book.