That may work okay for some places, particularly if your revenue stream is only loosely coupled to the code in question. Personally, the code I work on has a lot of revenue pushed through it every day, in a very quantitative manner. So, refactoring from what it does do to what it "should" do is fairly risky. What looks best to the developer isn't always best for the business, and even if a change is for the better any unexpected changes in the metrics raise flags.
YMMV, but I think that in a organization of any significant size, it's generally a bad idea for developers to make unilateral decisions about how the product should be changed.
-
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.
|