Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
I'll take the pragmatic approach. XP is meaningless -- I could pick out people with much less XP who are both better programmers than I and are better at Perl. Contrariwise, I could point out some higher level monks who still don't seem to get it. Don't even ask for the latter.
  • Efficacy -- does your code do the job? Is it sufficiently efficient and effective?
  • Extensibility -- when requirements change, how much work is it to add new features?
  • Maintainability -- to what degree can you or someone else fix bugs and keep the code running smoothly?
Fill in your own definitions for all of the adverbs. When you're satisfied with your progress on this front, you'll be well on your way.

A side note -- very few good programmers are worried about hurting feelings in code reviews, for good or evil. At the risk of prematurely associating myself with that elite group, I'll just say I want software that doesn't suck. I'll try to be nice about it, but I'm not going to mince words if you have a security hole or are (ab)using a feature too much. Now if you repeatedly demonstrate that you don't get it, you will get it. :)

Update: Higher level than *most* people, not me. Those four most definitely get it.


In reply to Re: monastic wargames by chromatic
in thread monastic wargames by mkmcconn

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others browsing the Monastery: (6)
As of 2024-03-28 21:46 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found