Re: [Lit.] Buffer overruns
From: Trevor L. Jackson, III (tlj3_at_comcast.net)
Date: 01/31/05
- Next message: ošin: "Re: Surrogate factoring, mysteries"
- Previous message: Brian Inglis: "Re: [Lit.] Buffer overruns"
- Maybe in reply to: newstome_at_comcast.net: "Re: [Lit.] Buffer overruns"
- Next in thread: Trevor L. Jackson, III: "Re: [Lit.] Buffer overruns"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 31 Jan 2005 12:11:30 -0500
jmfbahciv@aol.com wrote:
>
> Yup. I'm about 65% on the way of knowing why.
> Nobody has been exposed to raw gear is one problem.
> The other cause of the problem is nobody has had to build their
> software system from scratch.
It is not that case that "nobody" has done it. Some of us have. And
some of us have done it well.
One aspect of the people problem is the dilution of the knowledgable
talent pool by those without that kind of fundamental experience. Or
who think they have that experience, but never had anyway to tell
whether they had done it well or poorly. This problem is particularly
acute with programmers whose only experience is classroom programming.
The instructor often does not have the experience.
Learning to program does not mean learning language syntax. It means
learning to think in a particular way. And one part of learning to
program well is to be aware that on an instantaneous basis Murphy has
more control over your typing than you do. It is only by consistent
application of effort over long periods of time that we accumulate the
defense against errors and omissions.
/tj3
- Next message: ošin: "Re: Surrogate factoring, mysteries"
- Previous message: Brian Inglis: "Re: [Lit.] Buffer overruns"
- Maybe in reply to: newstome_at_comcast.net: "Re: [Lit.] Buffer overruns"
- Next in thread: Trevor L. Jackson, III: "Re: [Lit.] Buffer overruns"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
