Within the last year
Within the past 3 years
1 - 5 of 5 articles
This is not the sort of stuff Joe Rigo thinks is "hard core" technical writing, but when you see a bungled job you know it will have a telling effect on a long line of documents. In the last three weeks I have watched a nouveau publications department manager and a personnel officer hire two...
It is an unfortunate, but true fact, that many student programs possess the same quality of vagueness as the book in the above quote. It could take years to decipher exactly what the code means. I say this is unfortunate because these same students are the source for future business programmers.
The most distasteful job that can be given a programmer is requiring him to document his program. When he finally completes the documentation, it usually is unsatisfactory. Why?
Naming data items is the art of converting well-defining descriptions of data items into meaningful names. The data name is made meaningful by including essential elements of the description in the data name and by a consistent ordering of those elements.
Save this article to read later. You can see your Read Later on your DeepDyve homepage.
To save an article, log in first, or sign up for a DeepDyve account if you don't already have one.
Sign Up Log In
To subscribe to email alerts, please log in first, or sign up for a DeepDyve account if you don't already have one.
Read and print from thousands of top scholarly journals.
Sign up with Facebook
Sign up with Google
Already have an account? Log in
To get new article updates from a journal on your personalized homepage, please log in first, or sign up for a DeepDyve account if you don't already have one.