Change itself is always de-stabilizing.
RFC:MUST it be always?
Here you are then: Bug fixes are always destabilizing. They change the code and all change is destabilizing and, as the Great White Shadow teaches, change is to be feared. Therefore the practical necessity, lest one tread on the serpents of chaos, for making a valid business case in this market of synergistic tendencies toward the supreme bounds of workaday entropy hemmed by the ubiquitous market demands for profit realization within paradigm changing certainties of all battle-tested stripes. Waterfall! Sea change!!! {Cough} {Cough} Beware… You didn't know to be careful with important and visible systems before this moment—change management is a completely alien concept to absolutely all naïve elitists—but now you do!!!!11!!!11
-
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.
|