3 ms·
I agree with and understand this part: >.. when I’m getting started, I never know what X and Y are. > .. once you’re into maintenance mode," But, how does on
by mavelikara 17y ago
I agree with and understand this part:
>.. when I’m getting started, I never know what X and Y are.
> .. once you’re into maintenance mode,"
But, how does one know when maintenance mode starts? In the build something/release/add feature/release/add feature cycle, it is easy to rationalize that I am not in maintenance mode until it is late.
Of course, as davidw said above, no advice is better than "use your head" :)
- bsaunder 17y agoI think migrating from prototype to maintenance mode is a continuum. For some reason maintenance mode seems to begin (IMHO) some where around 60%--80% of work for version 1.0. At that point it's too risky not to be testing routinely and things should have settled enough that you could depend on some solidified interfaces. I like this approach to TDD. This feels more efficient than starting with failed test cases on day 1.