When I first starting get paid to program i made a bunch of mistakes like this. Thankfully my boss at the time was really into helping me learn from the mistakes. I ened up learning a lot about how to ask the right questions during the requirement process.
One of his favorite things to do in a situation like this would be to ask to use the code as intended ie in this case the stats you couldn't find. Doing this had two effects one it made me rememeber the mistake without having to berate me. I aslo ened up adding this to my QA process. After I get done with a piece of code I grab the requirements sheet and try the software based only on what is written on the req.
-
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.
|
