Comment Re:Terrible coding standards (Score 2) 430
Coders are too busy writing code and making changes to what they write to give time for accurate documentation to be written....
In the age of using github as a distribution and code changes between today and tomorrow, the documentation is suddenly invalid before it's written. Even then, it requires a lot of stupid questions asked by the documentation staff to coders who think they have better things to do.
You've just described an extremely flawed development model. For some reason you can still get away with this with documentation since it's still thought of as not all that important and can be done last. People used to think of security in the same way (and some people still do this), but 20 years of people saying you have to bake security in at the start has resulted in nobody seriously considering doing that as a last step. But yet we still think of documentation this way, by and large.
The point being, if you want documentation, it needs to be part of the process, and part of the job. If a developer changes a major part of how people interact with the software, everyone in the project should know about that and it shouldn't just be this big surprise at the end.