Lit. Buffer overruns 1724

job.

No, it doesn't. If you read these posts carefully, you'll discover that a lot of the mistakes are because people never maintained the code.

They are inseparable facets but a coder who has never had the job to maintain after a ship of his code will never learn the pitfalls of his tradeoffs. If he never maintains another programmer's code, he'll never learn about programming styles and that fixing bugs using the coding philosophy of the original coder is the least problematic methods of maintenance. Take a good look at People Pictures who buttume that code can be perfect; they have never been doing any of the tradeoff design work that usually prefaces the beginning of coding. They work only from specs that has already incorporated all of this work. The same thing is true with after product ship. There exists a lot of work that goes on behind the coders' back to build a maintenance infrastructure.

And worse yet, people who have fixed one bug in a released product buttume they have done "maintenance". This is also a daydream. Producing a patch for a product out in the field is about .0005% of maintenance work. Warning: I pulled this number out of my butt--it is probably less than that.

BAH

Subtract a hundred and four for e-mail.