Re: Which modules do you "allow" yourself to use for production?

2013-07-23 Thread Dirk Koopman
On 23/07/13 13:22, Abigail wrote: On Tue, Jul 23, 2013 at 12:43:05PM +0100, Dirk Koopman wrote: On 23/07/13 11:03, Abigail wrote: I sometimes express myself too forcefully. I am trying to suggest that there is a balance to be struck. Further more, I believe that a successful developer does this

Re: new Perl project / startup - Need advice

2013-07-23 Thread Pierre M
Good luck for your startup Bob, let us know how it goes (maybe on blogs.perl.org?) Avishalom Shalit wrote: my only advice, if you are promised anything, be promised it in writing. (I do know quite a few people from whom i would not require a promise in writing, but they are very much the ones w

Re: Which modules do you "allow" yourself to use for production?

2013-07-23 Thread Pierre M
Dave Hodgkinson wrote: > Don't use system Perl. Brew your own and make it part of the app. > I made a few bundles with Syntax::Collector. There's the ones that i use... - in all packages: strictures, autodie, feature, Carp, true - to change the syntax, like Method::Signatures (i keep them sepa

Re: Which modules do you "allow" yourself to use for production?

2013-07-23 Thread Abigail
On Tue, Jul 23, 2013 at 12:43:05PM +0100, Dirk Koopman wrote: > On 23/07/13 11:03, Abigail wrote: >> On Mon, Jul 22, 2013 at 09:39:33PM +0100, Dirk Koopman wrote: >>> >>> While I reckon prototyping is useful, you should be aware that when >>> dealing with people that have Pound note watermarks etch

Re: Which modules do you "allow" yourself to use for production?

2013-07-23 Thread Dirk Koopman
On 23/07/13 11:03, Abigail wrote: On Mon, Jul 22, 2013 at 09:39:33PM +0100, Dirk Koopman wrote: While I reckon prototyping is useful, you should be aware that when dealing with people that have Pound note watermarks etched on their glasses, prototypes have a habit of becoming (the rump of) "pro

Re: Which modules do you "allow" yourself to use for production?

2013-07-23 Thread David Cantrell
On Mon, Jul 22, 2013 at 09:39:33PM +0100, Dirk Koopman wrote: > And yes, I > would advise against producing production code that has lots of external > (CPAN) dependencies, especially if the normal path through those modules > touche

Re: Which modules do you "allow" yourself to use for production?

2013-07-23 Thread Ash Berlin
On 23 Jul 2013, at 11:03, Abigail wrote: > Doing extra work now in order to save costs later is a luxury problem. > Your first worry should go to actually being alive later on. When you're > starting up, your resources are limited, the work that needs to be done > ASAP is huge, and your income i

Re: Which modules do you "allow" yourself to use for production?

2013-07-23 Thread Abigail
On Mon, Jul 22, 2013 at 09:39:33PM +0100, Dirk Koopman wrote: > > While I reckon prototyping is useful, you should be aware that when > dealing with people that have Pound note watermarks etched on their > glasses, prototypes have a habit of becoming (the rump of) "production" > code. This, I

Re: Which modules do you "allow" yourself to use for production?

2013-07-23 Thread Toddy
Once you have decided what modules you need. Don't rely on installing them all directly from CPAN. Keep the exact versions of the module you're using in either your own CPAN mirror or packaged with your self-brewed Perl to simplify consistency across all of your environments. On 22 July 2013 23:3