I disagree, if not a visual design, then a design for the code itself is needed- well, it's needed for big enough projects. If one were to skip planning out the

I disagree, if not a visual design, then a design for the code itself is needed- well, it's needed for big enough projects. If one were to skip planning out the project and how to code it, one could easily mess up whatever protocol system there is an just code the entire system poorly. Sadly I did this once! I coded the entire thing, and it worked. No plans, no designs, no nothing- one bug, and the entire project was ruined because I didn't plan ahead and design my code to be flexible in the least. Basically what I am saying is that if I had taken a minute to plan it- I would never have had to rewrite LOTS of code. It's always a good idea to design something before coding, a visual of the project helps and the actual code structure outline helps. Moral of the story: Always have a design up front. I didn't have a design so the structure of my code was incorrect for the "visual" the other person had in mind, so it broke. If that visual is solid, especially when working with/for another person, then fewer mistakes will be made down the road.