You're taking my debate to the extreme. I don't mean researching the laws of physics for a ceramic heat shield. I mean reading the code for this and that ceramic heat shield which is in the wrong shape for me (set shape aside from physics a second), and understanding how it works. Then plagiarising the heat shield, to roll my own collage, more suitable for me.

I don't like these other things because I don't understand them - "I don't like these other things because I've tried to understand how to use them best, but it seems like more of a challange to write code which thinks differently than me"

I've finished planning... Now comes the implementation - Planning is very dynamic while coding. Planning is drawing itty bitty circles with names. It's deciding where the borders of what repsonsibilities the different parts of your code have. It's not how the code will work - that kind of planning does tend to break, i agree. I need this planning because otherwise i go a bit astray, and then I realize this will actually work very badly with the rest of the stuff, and i'm all frustrated because i have to do everythign all over again.


Surprising as it may seem I do share the ideas you propose here. It's just the proportion we differ upon...

-nuffin
zz zZ Z Z #!perl