Re^2: How do you program (again)?

I see, that's more or less the way I follow by now. My concern is that while I build tools and objects, I postpone the time when I write the actual program that will do "the task". Beforehand, I used to write a program that more or less did the task, then improve it gradually... easier, but hard to maintain.

Comment on Re^2: How do you program (again)?

Replies are listed 'Best First'.
Re^3: How do you program (again)? by spurperl (Priest) on Jun 03, 2005 at 07:13 UTC
One of the benefits of the technique I presented is that it's actually easier to reach a working program quickly. When you write in layers from the bottom up, you test each layer which is simpler than the whole program, and thus assure yourself minimal bugs (debugging usually takes more time than code-writing). When you write the next (higher) level, you rely on a tested lower level and have more confidence. Massive unit-testing along the way and you're set for a working, clean solution.	[reply]
Re^4: How do you program (again)? by wazoox (Prior) on Jun 03, 2005 at 07:20 UTC
Well, I'll need sooner or later to dig into Test... I always test my code as I write it, I simply cut and paste small parts in little scripts... That's not elegant but that works pretty well!	[reply]