based on everyones input here im thinking more this points to the fact that its all part of the development cycle.
the need for each piece to interact with the other, and influencing its continued longevity and fitness!
this cycle is indeed living, and the process we use to program and document should be a reflection of that
what i am talking about i guess could be summed up as an organic deign process, how to make such a system that could encompass this? im starting to get some well formed thoughts on this now, revision control and uml could make up a vast portion of this, along with ummf, i think something could be accomplished to help in this important area of development, that being the process , info gathering/deciphering , deduction/forensics and documentation.
-
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.
|
