View Single Post
Old 11-21-2012, 08:43 AM   #57
MikeB1972
Gnu
MikeB1972 ought to be getting tired of karma fortunes by now.MikeB1972 ought to be getting tired of karma fortunes by now.MikeB1972 ought to be getting tired of karma fortunes by now.MikeB1972 ought to be getting tired of karma fortunes by now.MikeB1972 ought to be getting tired of karma fortunes by now.MikeB1972 ought to be getting tired of karma fortunes by now.MikeB1972 ought to be getting tired of karma fortunes by now.MikeB1972 ought to be getting tired of karma fortunes by now.MikeB1972 ought to be getting tired of karma fortunes by now.MikeB1972 ought to be getting tired of karma fortunes by now.MikeB1972 ought to be getting tired of karma fortunes by now.
 
Posts: 1,222
Karma: 15625359
Join Date: Jul 2009
Location: UK
Device: BeBook,JetBook Lite,PRS-300-350-505-650,+ran out of space to type
Quote:
Originally Posted by HarryT View Post
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.
To be fair you only need to write the design spec if you are a programmer analyst, some programmers just get instructions.

I have worked with one analyst who laid out the whole design without knowing anything about programming (Surprisingly it was one of the better design specs I've seen).
MikeB1972 is offline   Reply With Quote