marmel75
Master Don Juan
- Joined
- Jan 4, 2012
- Messages
- 7,175
- Reaction score
- 5,571
When you first start out, that's definitely a good idea. I still do that for complex things but dor simpler things I just kind of see it in my mind the way I want to develop it.I’ll be looking forward to working on this synthesizer once school is out. Hopefully that’ll help me out with learning that skill. I’m sure it’s gonna be an absolute beast of a project, though.
School is definitely testing my determination with these programs lol.
Are you a proponent of writing out everything you want to do on paper or drawing a picture before you even write a single line of code? Someone told me to do that because if you don’t know what you’re trying to do, like you said, you’re sunk.
Also coding in small chunks. As in write a method and then test it with a small driver before you move on. Because if you try to run it all at once that’s just asking for several logic errors and like 200 syntax errors.
Yes, I test things frequently while I am coding, usually writing the tests, assertions, and exception handling as I go...I find its easier doing it that way than trying to write a whole buncj od code and then retroactively weiting the tests...because then you won't do it because it ends being a lot of extra code