comment on

I think it depends, in part, on where the scope of your responsibilities lie and what kinds of tools are already in use on your system and in what languages they are written. The rationale for this is that if you have to go beyond scripting administration tasks to debugging administration tools, you'll want to be familar with whatever language those are written in. For example, a lot of the system configuration tools on a Fedora/Redhat system are coded in Python, so knowing that might help debug those tools if you encounter a problem. On the other hand, if you're maintaining a Horde/IMP installation (or other PHP-based web interfaces), then knowing PHP will come in handy.

I wouldn't get too caught up in what language are "cool" -- I'd focus on what other languages are in use around you every day.

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

In reply to Re: Learning ***** as a second language by xdg
in thread Learning ***** as a second language by bronto

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.


Think about Loose Coupling
	PerlMonks