I have always found that strict and -w just get in the way when one wants something up fast. Generally when I do this kind of thing I find they complain about specifics which I'm sure are very handy in large hard to manage code, but as I am never in a position where I must write huge apps in perl... I find them more a hindrance than help.

I personally believe that you're perfectly right for definitions of "huge" involving... about ten lines of code. Specifically, the ratio hindrance/utility that strict and warnings give become relevant in:

• one liners;
• golf (unless the specific rules say otherwise, but I can't remember such cases;)
• obfu (but IME it's a pleasure when the code is compliant anyway.)

For anything but these cases, being under strict will most likely just require you to type some three more keys each time a new variable is introduced: something which is unlikely to make you risk a CTS in the first place and will likely save you many editing cycles to correct trivial but common errors, thus reducing the overall number of keystrokes.

Whatever, this is just what quite about everybody think too. Including those who beg to differ due to ignorance first, but then get to know better. Humanity is vast, however, and you may really be one of a kind...