I think you have it wrong on two counts:
and as usual, I disagree with you entirely (grin)
But thank you for feeding back, ALL feedback is appreciated.
If you can't justify the benefits of your approach towards your boss, turning to us is a bad technique.
I emphasize using Perl as a community language and am turning to you to get perspectives on an interesting subject about Perl software engineering.
What exactly is wrong about soliciting the advice of a respected bunch of peers on a subject?
Your argument regarding the MANIFEST is a strawman - you can easily write a Perl program to maintain your MANIFEST file.
make manifest does that already, now that I recall.
why do you think you need to install just for testing? Just run your tests using perl -I lib from your distribution directory and you're all set.
I dont mean testing the modules, I mean testing the (web/command-line) app which uses the modules.
| [reply]
[d/l] |
I emphasize using Perl as a community language and am turning to you to get perspectives on an interesting subject about Perl software engineering. What exactly is wrong about soliciting the advice of a respected bunch of peers on a subject?
Trying to use the community to overrule your boss is generally a bad idea. ;)
It's not that you are turning to the community to help. It's that your boss has already said what they think is the correct solution, and you want to refute that with a buch of comments from a website. Not a good plan.
I don't mean testing the modules, I mean testing the (web/command-line) app which uses the modules.
If you write good module tests, that should be a very short process.
| [reply] |
Trying to use the community to overrule your boss is generally a bad idea. ;)
I'm using the community to get a wider perspective on the issue. You seem to think I have a stake in the fire and a viewpoint to defend. You also seem to think he does. In the past, he has read documentation I have pointed him to and changed based on the validity of the arguments. For instance, he had planned to use Template to deliver our website but I pointed him to HTML::Seamstress and he changed to Seamstress.
It's not that you are turning to the community to help. It's that your boss has already said what they think is the correct solution, and you want to refute that with a buch of comments from a website.
You are putting intentions in my mouth that were never stated. And "a bunch of comments from a website" is a major putdown of the contributors to this thread. Here we have people, some of them worldwide respected experts, putting time into explaining and justifying their point of view and you want to devalue that as "a bunch of comments from a website".
I didnt say that was my plan of action. And it is not. I simply want to see what others think about a point of contention. And so far, the responses have been useful.
My intention is to grow into best practices from well-informed responses, not stay entrenched in my prior practices if they are clearly inadequate.
That being said, my boss is a staunch advocate of DBIx::Password and that led to my recent scorching critical review of that module.
I think next time, I will simply ask for ideas and opinions on various approaches and leave "who-said-what" out of it. This was supposed to be a scholarly discussion on an issue and I really didnt need to bring in that much context. Now, without any supporting evidence, you want to make false claims about my motivations.
| [reply] |