+1 - I've been doing TDD commercially since 2003 and as far as I can tell it's a great way to squash bugs. I'd be willing to write tests.
Sent from my iPad > On Feb 15, 2016, at 01:36, Sven Van Caekenberghe <s...@stfx.eu> wrote: > > >> On 15 Feb 2016, at 10:27, stepharo <steph...@free.fr> wrote: >> >> Sean I agree that TDD would really make sure that we can script such object. >> I do not know how to motivate people to do so. >> In bloc I started to write tests and I immediately found bugs. >> So it was positive and may be we should have a group of people writing >> tests. >> Now I have to finish the mooc and I was waiting that bloc stabilise again. >> Because I spent time writing comments and they are probably wrong now >> especially since >> writing comments on thing you do not master is a PAIN. >> >> Stef > > The first comments (class/method), explaining the design, API and > implementation, should always be written by the original authors. It helps > them as well, because trying to explain something in words help to validate > the design. > > Only in the next phase should overview/introduction/teaching/book > documentation be written by others who might be better explaining things. > > Documentation is absolutely necessary, especially for published code. > > Maybe someone should run the 'missing comments' statistics again over the > current 50 image ... > >
