How to Write and Document Code So That Other Developers Can Understand It
thinkinghard.com
thinkinghard.com
I write programs in pseudocode first then add the code underneath, keeping the pseudocode as a comment. The code I've written from 1984 to the present day is still quite readable, apart from a parser I wrote in Perl.
Ad I think the jury's out about writing tons of comments in the code. A full test suite is much more useful and asker to maintain
That said, however, most business code is there to serve a problem domain which the programmers do not understand implicitly. It is very necessary to provide the programmers with good documentation of the problem domain so that they can write the right tests. Without this documentation, the test suite will be crap and the programmers will be too scared to refactor the code. So documentation is very important but it must be the RIGHT SORT of documentation. As the brits in the audience will know, the WRONG SORT of documentation will lead to utter chaos and BIG BALLS OF MUD.