15 Dec
2001
15 Dec
'01
9:06 p.m.
Based on the investment in time, I'd say coding, compiling, and debugging are
<%5 of the job, and I'm referring to completed programs which, in every
conceivable way, adhere to the specification to which they were designed
completely to the extent that it is humanly, and with the aid of countless
machines, possible to verify. The documentation, which occurs before and after
takes up the remainder of the time. Unfortunately that's what normally is cut
first, and the coding suffers as a result, since the requirements aren't in
written form. Requirements are the set of things which the code must do, and
other than which the code must NOT do.
Dick
----- Original Message -----
From: "Ben Franchuk" <bfranchuk(a)jetnet.ab.ca>
To: <classiccmp(a)classiccmp.org>
Sent: Saturday, December 15, 2001 9:33 AM
Subject: Re: "Geeks" and licensing
"Jeffrey S. Sharp" wrote:
There's a big difference between writing code
to solve problems and being
a software engineer. Designing, coding, and compiling is only 40% of the
battle. Hopefully you're also spending some time planning and testing.
Also, don't forget the the heaping mounds of beaurocracy that you must put
up with, whether in the name of a software process or for just plain
corporate BS.
You mean like "If we needed it yesterday I'll ask for it
tomorrow"
--
Ben Franchuk --- Pre-historic Cpu's --
www.jetnet.ab.ca/users/bfranchuk/index.html