comment on

It's all relative. No doubt whatever you might release will be superior to Net::FullAuto for example.

FWIW I do encourage you to consider releasing at least one dist. It will not be 100% perfect first time but then nor is anyone else's. But what will happen is that you will receive feedback - this will come from CPANTesters, CPANTS, cpancover.com, etc. but also occasionally from users. It's all grist to the mill and by taking it onboard you and your code will almost certainly improve.

I was also somewhat daunted at first release but am now very glad that I did so. My code may never be as top-drawer as MIYAGAWA's but that really doesn't matter. In the years since then it has improved noticeably to me as a direct result and it has also made me less reticent in contributing to others' projects (whether with patches/PRs/MRs or reporting bugs, etc.). So, take the plunge - what do you have to lose?

🦛

In reply to Re^2: User Profile Element: CPAN author ID by hippo
in thread User Profile Element: CPAN author ID by jdporter

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl: the Markov chain saw
	PerlMonks