Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
I ... have just recommended a project with the recommendation to use Java where Perl would have sufficed. Betraying Perl like this to broaden my skill set is a terrible burden.

Technical decisions don't exist in a vacuum, and they rarely serve a single goal. When evaluating two technologies that are good enough (all other things being equal), there's no sin in selecting the one that enhances your (or the group's) skill base.

In any project, there are multiple goals being pursued. One goal is "ship the project". Another goal is "leave us set up for the next project". (This latter goal is one reason why projects bother to record so many intermediate artifacts.) Individuals who don't pursue a secondary goal of getting into shape for the next project soon find themselves moved into a technological backwater.

Things go awry when people don't balance the primary goal of shipping the current project with the secondary goal of setting up for the next one. On one extreme, you can stick with tools you're familiar with, arguing that they're "best", and avoid picking up new tools that are good enough. This way leads to stagnation. On the other extreme, if you always pursue new tools, you may never ship.


In reply to Re: Loyalty, Personal gain or Professional Integrity by dws
in thread Loyalty, Personal gain or Professional Integrity by hakkr

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 pondering the Monastery: (7)
As of 2024-03-29 15:10 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found