I've been writing a series of experimental prototypes recently; and I've noticed that as I try to add things to an existing prototype (instead of starting somet

I've been writing a series of experimental prototypes recently; and I've noticed that as I try to add things to an existing prototype (instead of starting something new), it becomes incredibly painful. I actually end up spending almost all the effort on trying to make it fit with the code I've already written. Reusing code seemed like a sensible thing to try to do (you should reuse code!), and the existing code itself was actually pretty clean - just not designed for what I wanted to do next. Therefore, I've decided in future to try out making prototypes that are strictly prototypes. If I want to try something new, I'll make an entirely new prototype. And see how that goes. At the very least, it will probably be more fun. :-) I mention this here, because of the article's description of "honeymoon code" vs. "maintainable code".