Rumor has it that Geoff Roberts may have mentioned these words:
>
>----- Original Message -----
>From: "John Allain" <allain_at_panix.com>
>To: <classiccmp_at_classiccmp.org>
>Sent: Friday, March 01, 2002 2:34 AM
>Subject: Write only programming
>
>
>> > Also reminds me of "programmers" who can "write code" but
>> > seem unable to read other people's code. Has anyone else
>> > had this experience? I run into this sort of person all the time . . .
>>
>> Youu could probably make a graph of "Write Only" languages,
>> those that allow you to get things done, but then don't explain
>> themselves very well when read later.
>> The graph would have CoBOL and Pascal on the left side,
>> and c and APL on the right.
>
>And JCL would be where? I class that as the ultimate 'write only'
>language.
JCL would be in the basement of my new house... I saved all of my JCL
listings when I worked at EDS (Generous Motors... ;-) back in '89-90, so
this is amazingly on-topic... ;^>
>> I can probably read anything,
>
>:^) Ah! You've never seen JCL have you?
Have *you* seen APL? JCL was/is a cakewalk compared to APL... and IMHO,
it's more readable than Lisp... but RPN was never my bag, anyway.
>Some programmers do this deliberately. It used to be considered 'job
>security'. ;^)
I used to think that way, until I had to fix some of my own "unreadable"
code to save *my own* job... afterwards I considered it "job SUCKurity".
I'm not the best with commenting nowadays, but I'm one helluva lot better
than before! :-P
Laterz,
Roger "Merch" Merchberger
--
Roger "Merch" Merchberger --- sysadmin, Iceberg Computers
Recycling is good, right??? Ok, so I'll recycle an old .sig.
If at first you don't succeed, nuclear warhead
disarmament should *not* be your first career choice.
Received on Thu Feb 28 2002 - 17:23:39 GMT