This may seem unfair or unimportant to some, but I know one problem we have here is English (or native) language skills. If I can communicate with my coworkers in plain speech, then it makes my job a whole lot easier, as we do a lot of phone conferences. It's very difficult to get what the customer wants--adding a language hurdle is one of those problems that I've found really slows down our development time. When his part of the project is mentioned in a meeting he does the same vapid nod, head-bob he does when you think he's understanding you... sigh...
We hire a lot of new guys here. All but one of our native speakers has been able to make significant contributions to our group(and the guy who didn't work out was a 15+year engineer who really should've retired 10 years ago...he's been moving from organization to organization, finding new and unique ways to do nothing for quite some time). It takes a while sometimes--sometimes just shadowing us, but it beats the shadow who can never tell me if they actually understood what I've been demonstrating.
-
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.
|
