Like everything else, there has to be a "point of balance". In this case, someone (the author of the quotation) acts as arbiter between what the end users want and what the "system" can or should provide. The ability to release new software daily does indeed reflect flexibility and agility. The question is how much flexibility and/or agility should be exercised?
Too much of these qualities expend resources that can never be reclaimed and will kill the organization. Insufficient flexibility/agility will kill the system, because: the users simply won't use it; or the organization will die because it could not adapt to the real functional needs it was designed to satisfy.
-
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.
|