I think these points are missing an important point that as a programmer it is part of your professional obligation to help create the requirements that you'll be working under to ensure that they are do able, make sense and will benefit your client. The way the original poster worded things it sounded as if things were completely out of his control. Obviously that's not true in any reasonable situation - I you were my teammate then I'd expect you to push back on things that don't make sense and help to guide things appropriately. Things still can still go badly but at least you'll have exercised your obligation to do a good job which is a larger issue than just having good code.
-
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.
|