Accumulating in software development it's a risk. Here are some examples:

  • writing a lot of code without compiling is a risk
  • writing a lot of code and AFTER writing unit tests is a risk
  • compiling many times without running the code is a risk
  • doing all this and never release to the end user is a risk

 

So the process of writing test, writing code, compiling, running, releasing is constituted by a set of rhythms: some are fast rock'n'roll (like the TDD: red, green, refactor), some are more a slow jazz (iteration, iteration, release, …).

So respect the basic rythms, find your tempo and keep it!

PierG

powered by IMHO 1.3

Advertisements