On Tuesday, July 16, 2002, at 08:46 , Timothy Johnson wrote:

> I have a few suggestions.
[..]

While I basically agree with most of timothy's thrust,
I would argue the case slightly differently:

        a) the outside world is full of beast creatures and demons
                with BIG FANGS and CLAWS - avoid it at all cost, and
                focus on staying inside with your computer and code - remember
                your computer LOVES YOU when you talk Perl with it.

        b) Use the perl beginner's list as a

                        "play along at home game"

                when someone proposes a problem, and more importantly,
                when someone proposes a solution - code it up, decide
                if you agree, or can 'beat' their solution.

        c) Never get involved in any way with anyone who is not
                coding in the language you are working on - or as I
                noted to co-workers,

                        "fine, but does she code in Java?"

                since the code-monkies were talking about mastering Java,
                and were at times distracted by 'gender appropriate persons'
                and totally spaced out Rule (a) above....

                In this case,

                        "If they do not Perl, YOU do not want to talk with them.
                                PERIOD!!!! They are DEMONS in Disquise!!! Avoid 
Them!!!!"

                return to your quest for the TRUE IMPLEMENTATION of Orthodox Perl.

        d) start with

                        perldoc perl

                read it all, prove which is your preferred solution for
                all of the currently available documentation that already
                exists for all things that perldoc perl will list.

                Read all of the References recommended, do the perldoc for
                all modules you have currently loaded.

        e) visit the CPAN, download each module in turn, decide for
                yourself by

                        e1. code inspection
                        e2. building and running
                        e3. proving that you have a better solution

                for all existing modules, and their potential modules,
                that you understand their strengths, weaknesses, and
                applicability across all platforms.

        f) Visit the ActiveState Folks, and Source Forge, look at how
                they are solving problems. Decide which of them are useful
                solutions, by demonstration.

        g) Look at coding solutions in Other Coding Languages, such as
                python, ruby, java, c, c++, vb, etc - demonstrate that you
                can actually do that better and faster and cheaper in perl.

        h) TRUST NO ONE! Trust only what you have coded and benchmarked
                yourself - even people who talk about Perl could be DEMONS
                IN DISGUISE trying to lead you into apostasy and evil, and
                pull you off the true path to the True Perl!!!

Go Thou, and Sin No More!

ciao
drieux

---


-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to