> a) not knowing what has already been done in Perl > a la the CPAN
A lot of my early work would have been spared if I knew that CPAN had EVERYTHING close to perfect that I wrote badly. > > b) other alternatives that exist in other open source solutions Eh... I let someone else do it as often as possible > > c) Wanting to just try to re-implement FOO to better > understand what is really going on in FOO I come across this often. Most of the time it's someone else's script that needs to made better. This is about 60% of my work. > > d) the documentation for FOO::BAR is not as clear as it > could be. > Docs? I don't think Docs are the problem... it's COMMENTS! 20% of work is trying to figure out why/what/how someone did something when a comment would have helped alleviate that problem. > e) "I am not really a software developer, but I need to automate > this little thing...." and hence > because perl is basically > that simple - "why not?" - and it just > grows from there... there goes the other 20% of my work. I am the PerlGuru at my company, (kinda sad). And all I do it write this and that for others most of the time, and then I maintain it, fix it, enhance it, etc... > > Hence how can we as PerlGeeks improve the overall process here? IMHO There should be a Perl "Let's get busy the smart way" Doc for really really basic crap like where things are and how to look for them. Documentation should be the first thing, where/how/why. Modules should be the second thing, where/how/why. External sources should be the third thing, maillists/FAQs/Books/etc. That would answer about 1-10 of the questions we see on this list everyday. ---------------------------------------------------------------------------- -------------------- The views and opinions expressed in this email message are the sender's own, and do not necessarily represent the views and opinions of Summit Systems Inc. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
