transputers again was: The dissolution of Commodore 2929
Yea, well. Since when did those people know about the real world?
That is a correct way when you have to think in batchmode. Thingie A has to be finished before Thingie B starts up if B uses A's output.
transputers again was: The dissolution of Commodore 2931
Joe Pfeiffer Hey, there have been people writing *bad* code for a long time. A friend of...
My courses reduced the grade by one if there was any error. So the only way to get an A and-or pbutt the course was to never make a coding error. I still think that imprinting caused me to become a "bad" coder because I had to write flawless code before setting it into bits.
However, this was the way IBMers had to do their coding (desk checking) because there wasn't such a thing as timesharing on card machines.
transputers again was: The dissolution of Commodore 2930
On Fri, 17 Mar 06 12:51:51 GMT in alt.folklore.computers, ^^^ ? The issue at stake tends to be whether you want to keep the old code exactly as is, or...
HUH?!!!!! That was extremely stupid.
Yup. That gives your equals and-or peons something to pull apart before you spend the next two manmonths implementing a bug.
Supervisors and-or project leaders can produce a conceptual flow chart. This helps buttign a box to each programmer. The Pert chart concept came out of this one. Flow charts can be work flows, bit flows, data flows, black box flows. I don't understand how anybody can design anything without doing one.
Alt Folklore Computers Newsgroups