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?
I tend to alternate. Breadth first, then alternating. Once I'm convinced something is actually a good idea, I'll start doing depth. Ideally you keep it simple and robust, so that you never have to go too deep. Maintaining that is hard. Takes thoughtfulness.
-
-
I do exactly this. Code as fast as possible to get the core idea tested and flush out all the niggly bits. Then do a bunch of passes over it to make it beautifully simple.
Kiitos. Käytämme tätä aikajanasi parantamiseen. KumoaKumoa
-
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.