Jan Coffey wrote:
*sigh* I know I must have made some syntactic mistake their myself but, hay,
I'm just as human as Erik.
Erik's Human?
Huh.
Doug
8^)
___
http://www.mccmedia.com/mailman/listinfo/brin-l
Jan said:
Unless requested by a client or an employer, the code illustrates how
the finished code works.
The only problem with that is that the code can only illustrate what it
actually does rather than what it should do. That's why it's so
important to have comments that give the intention of
On Thu, Jun 12, 2003 at 10:00:27PM -0700, Doug Pensinger wrote:
Erik's Human?
You haven't figured out yet who I REALLY am?
--
Erik Reuter [EMAIL PROTECTED] http://www.erikreuter.net/
___
http://www.mccmedia.com/mailman/listinfo/brin-l
Jan Coffey wrote:
So Rich, don't blame a lack of documentation for poorly factored code.
Instead of If these idiots would just have documented..., think If these
idiots would just have writen Unit Tests or Contracts, written clear code
with short methods and discriptive naming, used codeing
Ronn!Blankenship wrote:
At 10:00 PM 6/12/03 -0700, Doug Pensinger wrote:
Jan Coffey wrote:
*sigh* I know I must have made some syntactic mistake their myself
but, hay,
I'm just as human as Erik.
Erik's Human?
Huh.
Doug
8^)
Let Us Oft Speak Kind Words
Text: Joseph L. Townsend
--- Dan Minette [EMAIL PROTECTED] wrote:
Hypothesis: A tentative assumption made in order to draw out
and test its
logical or empirical consequences.
Theory: A scientifically acceptable general principle or body
of principles
offered to explain phenomena.
I would only add
--- Ronn!Blankenship [EMAIL PROTECTED] wrote:
At 01:51 PM 6/12/03 -0700, Jan Coffey wrote:
--- Dan Minette [EMAIL PROTECTED] wrote:
Hypothesis: A tentative assumption made in order to draw out
and test its
logical or empirical consequences.
Theory: A scientifically
