Re: avoiding writing readme for scripts

[KM]

When Larry says a virtue is to be Lazy, he didn't mean to be a Lazy SoB. Part of programming is to write the README files so users know how to use the stuff you write. Not everyone can read Perl, or read everyones style of Perl and the README helps to remedy this. If you used POD within your script, you could extract it.. otherwise, it would be good practice, especially for a student, to write a decent README for your script. Sometimes when writing how to use a script you can see things that don't make sense, aren't obvious, and things that in general would be good to fix. So, do everyone a favor, and write your README.. it is not programming, but still the work of any respectable programmer (IMO).

Cheers,
KM

[tilly]

In fact Larry wants you to turn all of those normally bad things into virtues by doing them in an enlightened manner.

Have hubris but maintain it intact by being good enough to justify it.

Be lazy, but think ahead to anticipate demands on your time and head them off in advance. For instance it is less work to write good documentation then call RTFM than it is to answer questions.

Be impatient but take it out by getting to good answers fast rather than complaining.

In other words let each deadly sin redeem itself by motivating you to act in a virtuous manner. :-)

[Anonymous Monk]

its not that i'm lazy... its just i'm patiently challenged. Boy you guys answer these questions really fast. That's amzing.

[redmist]

NEVER feel bad about being lazy!!! It's the American Way! (That and it makes everything soooo much easier.)

redmist
redmist.dyndns.org
email::redmist