Yet, how on earth will your code improve without public use? I know my coding styles and abilities improved greatly after releasing stuff to CPAN. Put it out there! People will see it, use it, and get back to you with what they liked and didn't like.
Here's another thing - I know my biggest issue is interface. The first question I ask anyone who comes onto the Excel::Template mailing list with a suggestion is "How do you want to use that feature?". They describe their desired usage, someone else brings up their desired usage, and I add in my knowledge of the rest of the features. Eventually, we come to a consensus. Once that consensus is there, it's cake to write the feature. At least 50% of the time spent in writing F/OSS is figuring out what to write. The actual writing/testing/documenting is a lot easier once you have that figured out.
Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.
| [reply] |
