||Jun 09, 2006 at 15:47 UTC
||Nov 30, 2015 at 23:55 UTC
(10 hours ago)
|Location:||North FL, USA (a.k.a. Gator country, middle of nowhere)|
Dec 01, 2015 at 04:41 EST
|For this user:||Search nodes|
The subject of the image above is an early Mercedes Benz 300SL. It was sourced from Wikipedia's 300SL article. This, in my opinion, is one of those truly rare pieces of functional art.
If you have read nothing else, read these:
When your toolbox is limited to "hammer", you try to refactor all problems into "nails". This is the wrong approach. Don't be afraid to look for new tools for the box. The flip side of this is sometimes the fine hammer is the best tool. Wisdom is being able to discern between the two. The quicker you get to that point, the better off you and those who work with you will be.
Most useful hash reference I've found
a useful CSS reference
Writing unicode text docs with perl
TKX basics and documentation
XMLTwig.org reference by author mirod
I use YAML for as much machine to machine communication as is practical. Here's why.
Whenever I think I'm having a bad day, I think of the poor sod that left the footprints in this photo.
Modules I use on a regular basis:
Speaking of POD, here is a useful template.
- Log::Log4perl. Quit your homebrew logging. It probably isn't as good as Log4perl.
- YAML::AppConfig. Standardize your data serialization, even in your program configuration files.
- WWW::Mechanize. Browse the web, headless.
- Test::More. Start putting tests in your work. Get started with Test::Simple.
- Net::FTP::File. Fill the gaps in Net::FTP.
- XML::Twig. I haven't found a need for any other XML processor. Exceptionally powerful and usable.
- GetOpt::Long. Make passing switches and data into your scripts easy.
- File::Spec. Never worry about how paths are built again.
- Pod::Usage. Use POD for documentation. Get it somewhere your users will see it.