Ready the flame retardant! I know there are monks who don't like Dist::Zilla...or my modules... or me... But in the past such criticisms have only served to make me a better Perl hacker than before I was criticized, and (more importantly) guided me to improve my code. I fear the day when people stop offering me negative feedback (because that will probably be when I'm dead HAR HAR). So:
A couple of days ago I moved File::Util to git+Dist::Zilla, and added Perl::Critic into the mix. This was on my list of resolutions, but not just for the new year. It's more because I think I owe it to the community to keep offering better things and generally never cease trying to improve.
Euphoric Observations and Kvetches:
- git is so frikkin easy; you're over-thinking it-- just type "git" and you'll "get" it (how anyone manages to write a whole book on something so simple is a real puzzler)
- Dist::Zilla was a pain in the *censored* to get working, but it really was worth it, especially with the many plugins that make being a CPAN author waaaay more easy and fun
- Perl::Critic is mean (wah ;_;). I like to eval 'expressions'; Perl::Critic does not.
- Perl::Critic cites the Perl Best Practices book for everything it complains about. The book is not free, and the references to page numbers are USELESS when you decide to shell out the money, but buy the more budget-conscious kindle version instead. Kindle doesn't have real page numbers! Hello McFly!
- Dist::Zilla fosters and facilitates "kwalitee" (as in CPANTS) by generating/maintaining certain "meta" files that you might forget to add or update before packing up your dist. (version control and the MANIFEST admittedly help with the "add" part, but Dist::Zilla still has your back in this regard, should you mistakenly un-add something that should be there)
- My CPAN modules will from now on have much better kwalitee, pass Perl::Critic tests, include git repo info, build more easily on platforms that don't have a "make" utility, add a Module::Signature to all builds, and other lofty devel snobbery that I haven't yet added to the mental list
- The next Perl Mongers meeting will be more fun now that I'll know what I'm talking about as I cover the scheduled topic (collaborative development with git) :-D I'll also be supplementing the curriculum by showing merlyn's presentation video on git which he shared very recently on google+!
That is all.
And with the new year, these resolutions begin to unfold. Over at a new github repo, items are getting checked off the TODO file while I pour another glass of non-alcoholic sparkling white grape Martinelli's
$ perl -MMIME::Base64 -e 'print decode_base64 "YWNlQHRvbW15YnV0bGVyLm1lCg=="'
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] |