Why questions don't get answered, or "No, I've already RTFM, tell me the answer!"

[Mike McCarty]

David G. Miller (aka DaveAtFraud) wrote:

> Ever since serving said sentence, I have been of the opinion that all 
> newly minted programmers should first serve time in the purgatory known 
> as "software maintenance programming."  Only after getting an 
> appreciation for how hard it is to divine someone else's obscure code 
> should they be unleashed on the world and allowed to create their own 
> inscrutable incantations.

Agreed. Hewlett-Packard used to have a policy that, for 1 month a year,
all sowftware development engineers had to work answering field
problems doing phone-in support.

> That being said, I probably do most of my current development in perl 
> which has been described as a "write only" language.  I prefer to call 

Nah, that's APL. The first high-level programming language I learned.

> it the Swiss Army Knife of programming languages.

Mike
-- 
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!