Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw
 
PerlMonks  

Re: Dallas/Ft Worth, TX Perl Mongers Reboot Today 12/12/12

by Tommy (Chaplain)
on Dec 13, 2012 at 16:21 UTC ( #1008681=note: print w/replies, xml ) Need Help??


in reply to Dallas/Ft Worth, TX Perl Mongers Reboot Today 12/12/12

Last night's meeting was a big success. That's right, I said it.

I, for one, had a great time and enjoyed mongering with my fellow... er, mongers. It was good to see some new faces as well.

I am very pleased to see new life getting breathed into the group. I see lots of great things in its future. We've got some really cool plans on collaborative projects and Patrick Michaud, the Perl6 pumpking, had some great suggestions last night as well.

All I can say is, WOW, that was awesome. I can't wait for our meeting next month! Every second wednesday is the official schedule, and as always, YOU are welcome and invited.

--
Tommy
$ perl -MMIME::Base64 -e 'print decode_base64 "YWNlQHRvbW15YnV0bGVyLm1lCg=="'

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1008681]
help
Chatterbox?
[stevieb]: perldigious You should start by writing some unit tests. That'll ensure current functionality doesn't break with changes.
[choroba]: unit tests++
[choroba]: The only problem you can't solve by adding more tests is the problem of having too many tests.
[stevieb]: choroba Been there, done that :) Better too many than not enough though!
[stevieb]: I very often write a base set of unit tests before writing any code. It helps dictate the API, and ensures my earliest of ideas stay on track.

How do I use this? | Other CB clients
Other Users?
Others exploiting the Monastery: (10)
As of 2017-07-21 20:03 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    I came, I saw, I ...
























    Results (335 votes). Check out past polls.