++ tracking performance with timesheets is not a good thing at all. But I had the unpleasent experience of being mesured that way.
The result was that people started to simply to be on time with "implementation" by skipping parts of it and the things that weren't finished in the initial coding phase was pushed on to bug-fixing(unfinished implementation details are bugs right?). The result of this was a drop in code quality because the allocated time for bugs wasn't enough due to the covering of the delay in the initial implementation of code.
Time based metric is even worse than LOC count measuring.
-
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.
|