-- Randal L. Schwartz, Perl hacker

Drinks Per Invitation?

Deciliters Per Inbibing?

Drams Per Icecube?

Only kidding... ;-) (Party safely...)

--f

One of the most compelling practices of XP is the heavy focus on unit tests. In fact, you're supposed to write the tests before you write the code to pass the tests.

I'm resolving to try this, especially with my Perl Rogue project. (It'll be easier to write unit tests for existing Jellybean code after I have some practice with tests in general.)

Update: I put in the words that jlp pointed out were missing. Don't stay up late and type, kids.

You might want to try out Test::Unit, the Perl port of the XUnit framework for unit testing.

If you install the module via the CPAN module, please take a look at the build directory, it contains some examples for common ways to use the module.

Christian Lemburg
Brainbench MVP for Perl
http://www.brainbench.com

The beginning of last year was really awful, but started getting better in the last half. Perlmonks gets some credit just by being such a open, warm, and damn useful site. This year is looking real bright.

Well, if nothing else, I'll reply to this with my Perl resolutions for the New Year so that they're "in writing". :)

For 2001, in Perl, and as a programmer/wannabe hacker in general I resolve to (in no particular order):

• Join an interesting free software project (something that I think is neat, that is also a piece of software I'll use when all is said and done)
• Submit a useful module to CPAN
• Ensure that I read every piece of relevant documentation I can find before accidentally expecting that someone should repeat the FAQ to me (I basically do make sure I've read everything I can think of already, but I want to make more a point of it from now on anyways)
• Ensure that the advice I give as a programmer to a programmer is precise and helpful (again, this is basically something I do already, save for the odd time where I do admit to making "general" types of comments in subject areas for which I might not have very much background in)
• Become more "active" in my role as a software user. This would include becoming an active bug reporter/fixer, and not being afraid to voice my opinion to vendors/other programmers/hackers about things I don't like or do like in their software, and heck, maybe even doing something about it myself! :)
• Help others out more on clpmisc and here when I am smart enough to do so :) I admit that a lot of what I do is "lurking" with not enough giving answers to questions for which I know the answer
• Get better at being truly lazy (always grep, never repeat a task where a piece of code could do it for me, never type more than I need to, never ever write code for tasks that somebody wrote a module for already, etc)
• Avoid engaging in flame wars, especially language wars. The right tool for the right job!

It's a fairly big list, but many of these can be done concurrently and work together.

And for the record, I'm going to link to this node from my home node so that fellow monks can check back with each other 3-4-6 months from now and see how we're all progressing :)

my officemate convinced me to go to damian's OO tutorial at the perl conference this summer, so since then i've been meaning to actually put some of that new knowledge to work. sadly, everytime i have to write some new code, it needs to be done yesterday, so i just wimp out & write it the way that i normally do. sigh.

• to submit a useful module to CPAN.
• to submit bug reports and fixes to module owners.
• to pick a login that isn't an adverb or a single character like =.
• to using more descriptive variable/sub names rather than trying to get them to spell out amusing sentences later in the code.
• to either write the YOU module or change my sig.
• to meet at least 2 perlmonks in person and buy them a beer/drink. (I still owe jeffa one...)
• Close all my HTML tags =P

--
$you = new YOU;
honk() if $you->love(perl)

Perhaps you should resolve to close all of your HTML tags. (:

        - tye (but my friends call me "Tye")

I resolve to
Tackle tye.
Downvote tye as often as possible so he can enjoy changing levels often
Find some way to kidnap tye and reenact the movie/book Misery. ( Tye You're not squeamish are you? )
Eat more pecan pie
Steal all pie from tye.
Stop posting to Perlmonks after the caffeine hits hard


Everyone has their demons....

1. Buy and read Network Programming with Perl and Data Munging with Perl.
2. Not get fired from my switch n' router job for spending too much time learning Perl.   {grin}
3. Update: Spend enough time AFK to stay (get?) outa trouble with da missuz. {still grinning}

- p u n k k i d
"Reality is merely an illusion, albeit a very persistent one." -Albert Einstein

• keep working on the Outside Links page (thats easy)
• giving Niederrhein.pm a good start (thats more difficult)

neophyte

I also resolve to double-check my spelling before posting.

Oh hell. I resolve to lose 30 pounds by the end of the year.

• Actually start learning Perl ;)
• Go have a beer with extremely and notsoevil
• Swear off red-headed girls (what does this have to do with Perl - they keep me from studying, that's what)
• Start mixing MIDI with Perl (er, mixing in the programming sense - not sound mixing)
• Steal merlyn's brain (or at least rent it for a while - of course, tye or tilly's would suffice as well . . .)
• Excercise - it really does do wonders for the brain, not just the body

Jeff

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
F--F--F--F--F--F--F--F--
(the triplet paradiddle)

• Use the bare minimum number of modules nessisary.
• Write more Gimp PerlFu scripts!!!
• Try to pay off the bills. Damn credit card...
• Rewrite random items in Perl.
• &convince($merlyn,&&to($talk)(&like($this)));

--
$Stalag99{"URL"}="http://stalag99.keenspace.com";

Celebrate Intellectual Diversity