I suppose I'll put in from the perspective as a prospective interviewer. All other things being equal, I would likely look at certifications as an area that you've shown interest in. However, all things are rarely equal: I would worry more about your actual accredited degree from a reputable university or college (as may be applicable to your country - colleges here in Canada are usually not accredited degree-granting institutions, unlike in the U.S., and I know nothing about the U.K. system), and your in-field experience. Even if that in-field experience is open source. (In some ways, that's even better, since I can go and look at samples of your code, buglists, etc., before the interview - we can then go over your code with some really technical questions!) I want to know what you have done, and how that makes you a better candidate for the position I have to fill. Certification rarely answers that question.
-
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.
|