OTOH, it's not unreasonable to mandate that applicants have some specific free software contribution they can point to as an example. This shows several things. First, it shows that the person is geek enough to enjoy coding on their free time.
Actually, as an architect that is part of the interviewing team, I've found that the best programmers we've hired are people that do have outside interests. When they go to program, they bring the wealth of other experiences with them.
Not only that, but those who spend the majority of their time coding seem to lose social skills which make them a viable part of the team atmosphere we engender at work.
-
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.
|
