The biggest failing I see with programmer B is his careless attitude
in putting off everything until Monday morning, which is risky with a
Tuesday deadline. Had his Monday morning search not turned up a
suitable existing wheel he may well have missed the deadline. I'd
rather hire programmer A and teach him to incorporate searching for
prior art into his current plan and design phase. Programmer B seems
to have a sloppy attitude even if he got the work done this time.
Now, had B done the google search Friday evening, found a suitable
candidate, determined he could use it to easily finish the demo on
Monday, then that is a different scenario altogether. Of course, if
Tuesday deadlines are often given at 4pm Friday without consultation,
perhaps both A and B should invest some time in seeking out other
employment opportunities.
-
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.
|