In industry one standard step is a code review--by one or more peers
who will subsequently support the code
Donna
[EMAIL PROTECTED]
On 17-Jun-06, at 3:33 PM, Ralph G Selfridge wrote:
While this topic seems to have got wider let me add one more point.
Several have mentioned the effects of bad coding practices, whether
J or APL (or the other pornographies). A large part of that is
caused by how we (schools/Universities) teach software writing.
Somewhat like learning to write English it seems to take a
competant reader to look at the code. Almost none of our
institutions have the man power to do that, I even suspect there
are graduating people who have never had their software looked at.
In one automated software grading of software the software had to
follw a rigid format in order for the 'grading software' to work.
Unfortunate
Ralph S
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
