Not funny anymore
- Feb 6, 2008
- Reaction score
Sounds like quite a different kind of university than our guy went to. Could I have somebody from that university, please? Because that all sounds very appropriate... (though one can overdo it on the documentation front IMHO. I tell my developers that they'd rather invest time in making their code readable rather than into documentation to make sense of an incomprehensible mess...)
I agree there mostly. Of course, if you do large business software and complex distributed systems, you have a different idea of what "less documentation" really means.
But if I need to read 5 pages of documentation to understand what the implementation of a business rule does, something is going the wrong way. The principle of the least surprise is a very important one. All I really need as documentation are "cooking recipes". How to setup the build environment on a new machine? How to get started for programming? How do deploy on the test system, who to call for deploying to production? What happens if the new version is rejected from production how do we go on? When I translate a business rule - what is the domain language? What is the domain model that we are working with?
Any kind of documentation you write, is automatically as important as the source code. If your documentation is not that important, why did you write it in first place? Same applies to tests. If you carry with you 2000 unit tests, that all fail for years, why didn't you delete them?
The best tests are tests, that you really care for.