Re: Reading Source Code
From: deech_99 (deech_99_at_yahoo.com)
Date: 04/27/04
- Next message: Malcolm: "Re: Interview Impact of Years On First Programming Job"
- Previous message: Edward G. Nilges: "Re: Simple Parser"
- In reply to: Ben Pfaff: "Re: Reading Source Code"
- Next in thread: Ben Pfaff: "Re: Reading Source Code"
- Reply: Ben Pfaff: "Re: Reading Source Code"
- Reply: Chris Sonnack: "Re: Reading Source Code"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 27 Apr 2004 17:25:18 -0400
I agree that diving into code is probably the best way of getting to grips
with the program and becoming a better software programmer.
My fear was that I would get into a 'badly-written' program that would
instill bad habits. I have been warned by other programmers that good
programs in the eyes of a user are not always good programs in terms of
exemplifying good programming practices.
Perhaps the best way is a two-pronged approach where
1) A 'classic' program (eg Tex or Linux ) is studied with
the aid of a book
2) I fearlessly dive into a more recent program which I
wish to extend.
On a broader scope I would like to know why the practice of reading
real-world code is not more widespread. In all other crafts the formative
years of the student are spent learning what has already been done- a jazz
musician, for example, studies others solos, and a writer is constantly
reading. Why is it that programmers do not study other's source code as
diligently?
Naively yours....
Deech
- Next message: Malcolm: "Re: Interview Impact of Years On First Programming Job"
- Previous message: Edward G. Nilges: "Re: Simple Parser"
- In reply to: Ben Pfaff: "Re: Reading Source Code"
- Next in thread: Ben Pfaff: "Re: Reading Source Code"
- Reply: Ben Pfaff: "Re: Reading Source Code"
- Reply: Chris Sonnack: "Re: Reading Source Code"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|