comment on

The perlmonks site, and perl itself, seems to follow the lazy developer vein. It's not bad as a general practice, but not it's horrid as an absolute one.

1) If you want something badly, do it yourself. Most monks, myself included, won't do anything w/o insentive.

2) perlmonk's code is in the db. read that again. there's no source repository you can download it from. Sure, they diffs are IN the db, but you can't download it and hack at it. It's a case of the tools inhibiting the developer. perl itself seems to have this problem.

Honesetly, your request will only teach you to query for pmdev status and then have to be very self motivated. There's no comradeship to help promote ideas.

You won't see shiny new ideas implemented much here, outside of modules. The effort to make things pleasant is just not there.

In reply to Re: Process for Site Improvement by Anonymous Monk
in thread Process for Site Improvement by ELISHEVA

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.


There's more than one way to do things
	PerlMonks