On 20 July 2014 09:33, Harry Putnam <rea...@newsguy.com> wrote: > > So all and any ideas, suggestions etc would be well received on this end. > > One approach that may help is to double down on CPAN. This may reduce the total number of tricks you have to learn, by finding proxies that do the tricks for you.
for instance: - learn to set up a local perl installation with either perlbrew or local::lib - learn to install modules with cpanm And after that point, a lot of things that might be tricks for you now, may be easier to implement in terms of a CPAN module. For instance, a lot of my IO memory is now freed up for other tasks since using Path::Tiny. It handles enough of the common cases with straight forward and well documented syntax that I don't really need to remember how to do it any other way. And for instance, I no longer much *need* to care about how to do OO correctly, because there's a lot of good modules that make this straight forward ( Class::Tiny, Moo, Moose , etc ) Another poster referred to "keeping an index of scripts", and in a sense, that's what CPAN is, just a much better organised much better structured, shared collection of script components. Perhaps some problems you may solve yourself locally may also be amenable to being CPANized, which will help you later when you need to re-use that trick. -- Kent *KENTNL* - https://metacpan.org/author/KENTNL
