Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

jshirley (7627)

jshirley
  (email not shown publicly)
http://www.coldhardcode.com/
+ -

  Comment: A Small Feature Request (Score 1) on 2010.03.22 20:58

by jshirley on 2010.03.22 20:58 (#71789)
Attached to: The Basic Unit of Bug Report Frustration

You may already be planning on this, but I'd just like to explicitly bring it up.

Please also address the "barrier to enter", and consider lowering that particular bar.

Since so many bug reporting guidelines and systems require a significant investment on the part of the user. If I'm simply evaluating some software, and I most likely will not be using it again, I won't be bothered to register, submit a bug and follow through with all the steps.

However, if there is a *simple* and well-addressed mechanism for submitting problems I'm more inclined to do it.

To put more personal context on my request, I'll share an incident that illustrates this from my real history. I was evaluating puppet and became frustrated at the stupid error messages. Looking at their bug tracker, there are no guidelines or any links labeled, "Report".

So, guess what? I didn't do it and don't have a shred of guilt or remorse. Why would I bother? I wasn't impressed enough with puppet even if the error messages were fantastic to be. Instead I posted on twitter about it, with enough detail on the particular error message (involving template errors).

Response? "Here's a link to our bug tracker, submit an issue". Fail. Er, I mean, #fail.

Read More 5 comments
Comments: 5
+ -

  Comment: Nothing, that's what makes it dangerous. (Score 1) on 2009.01.26 21:07

by jshirley on 2009.01.26 21:07 (#67024)
Attached to: I do appreciate the effort...

There is nothing that the EPO is doing that couldn't be done by others, but it can be said that the difference between a successful entrepreneur and a failure is simply doing it.

If the EPO fails and collects dust, some will say that it is a failure. I'll view it as a learning experience about what to fix the next time something comes around.

Also, my focus on EPO is to help Perl's external facing image. The EPO Extended Core is good for the various Best Practiceâ„¢ stuff, but the marketing is where I'm hopeful.

Perl's a great language, but with a horribly dense echo chamber that few people want to enter. Enlightened Perl's success will come easier with the Perl Community (or rather, a part of the Perl community; I don't think it is possible to have the whole thing ;)). However, marketing to the outside world doesn't really require support from the community, outside of the community not actively trying to hurt the effort.

If I can get people who have never used Perl to evaluate something, I'll view my time as a success.

Even if it is just a temporary fad... who knows, it may only last until Christmas.

Read More 31 comments
Comments: 31