> Working software over comprehensive documentation
and use it as a reason not to do documentation at all. It's ambiguous, and can clearly be read as "you should not work on documentation when there is software to work on", and there's always software to work on.
> Working software over comprehensive documentation
and use it as a reason not to do documentation at all. It's ambiguous, and can clearly be read as "you should not work on documentation when there is software to work on", and there's always software to work on.