Quote:
Originally Posted by tompe
Well, I work at a university and do not write requirement specifications. Writing maximally clearly often requires duplication of information. But it is very bad to have duplication in code or in design documents. Even requirement specifications should avoid duplications.
|
Absolutely. Each section of the system should be described once and only once. I would still maintain, though, that the ability to write clear and easily-understood English (or whatever language it is you're writing in, of course) is an absolutely essential aspect of the job of a programmer - at least if you want to do well in the customer-facing aspects of the job that are a fundamental part of it for anyone working in a commercial environment. You're not going to be able to win work from customers unless you can present your proposed solution to them well.