Has anyone done much "breadth first" programming? Write what you need only as you need it, error handling and fleshing things out as needed. I'm used to depth first, cause stuff tends to be swiss cheese if you don't finish it fully, but coding as needed improves speed. Thoughts?
-
The problem I had with fleshing things out as I went is that I kept having to switch mindsets. One minute I’m writing game code, then back to my rendering code, then over to my asset handling code. It’s nice to focus on one thing at a time.
This. ^ If there was something I knew I would get a lot of mileage out of, I’d do deep first. Often when I’ve written something like it before and I know what I want. Asset loading was this for me.
