Coding is only about 50% of the problem. The rest is getting people to understand and solve the problem as a group. I recall when I was in college I used to detest group projects, because the quality of the group you got to work in varried greatly. At work, likewise, espeically as the project gets larger and more complex, the more time you will have to spend communicating your ideas, and learn how to effectively navigate human interaction problems. If you can't explain to other people the scope of the project you're working on and why it's important, don't expect project managers to gleefully say 'go forth and conquer', until you have the paper trail to back your idea up...
-
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.
|
