This has kind of been touched on above, but bears expanding on.
A high-leverage real-world skill that I've seen lacking in fresh grads is the ability to make sure you're solving the right problem. This implies developing the ability to listen carefully and ask tactful questions, to spot gaps or inconsistencies in requirements and probe those gaps, and to resist prematurely charging ahead mentally on a design any further than you need to probe the requirements.
I've seen quite a few fresh grads sink weeks into solving the wrong problem. I see this less often with experienced folks, which may mean that they've learned, or it may mean that they've been culled from the development gene pool after solving the wrong problem one too many times.
-
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.
|
