> -----Original Message-----
> From: Conrad, Bill (ThomasTech) [mailto:[EMAIL PROTECTED]]
> Subject: RE: Reading versus Referencing Books
>
> Learning from someone else's code is not a good idea if it is not
> well documented and the code is poorly written. I like to write
> sample code
> as I am learning a new program to demonstrate statements and
> function and to
> document what it is doing. I then use this as templates when working on
> projects.
>
Which is why I always recommend looking over the reference material to
learn the "how and why" of each snippet of code I look at. Whether the code
is "poorly written" or not, 9 times out of 10, going back to reference
material will point out the obvious problems, and you've learned from
*others* mistakes. Less guilt with all the benefits. :)
>
> Always remember to document your code well so the next person can
> learn better from what you have done.
>
DEFINITELY a GREAT suggestion for ALL new programmers. Heck -- OVER
document if you're gonna swing to one extreme or the other. I'm dealing
with a situation at work now where I'm having to go back and modify someone
else's' code. There's not a LICK of documentation. And it's taking 3x
longer to get what I need done because I have to go back and analyze their
code/logic such that I can modify it for my needs. Definitely a hassle in a
production environment.
++========================================================================++
|| UNIREZ, Inc. Scott Thompson ||
++-------------------------------------------+----------------------------++
|| Address: 2555 Southwest Grapevine Parkway | Title: Programmer ||
|| Suite 200 | Phone: (817) 416-5800 ||
|| Grapevine, Texas 76051 | Extension: 104 ||
|| Fax: (817) 251-9199 | Cell: (972) 342-5660 ||
|| Web: http://www.unirez.com/ | Email: [EMAIL PROTECTED]||
++===========================================+============================++
