The quality of programming is quite variable. In years of programming, I learned by trial and error much that we train beginners, or at least try to, to do. Working in a team with disciplined standards also helps, as well as careful testing of each module before acceptance into the project.
We tend to give a bit more thought to our code if it has been specified in detail in a mark-up language and the tested result is examined by the team as a whole for flaws, line by line. I've written some rat's nest code that, ten years later, I couldn't remember what I was doing -- testing some algorithm, I suppose. My overlap integral routine is probably still in use 30 years later. Hard sciences still have FORTRAN as their lengua franca. Choppy At 09:15 PM 4/10/02 -0500, you wrote: >----- Original Message ----- >From: "Dustin Puryear" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Wednesday, April 10, 2002 8:57 PM >Subject: Re: [brluglist] windows sucks > > > > At 08:24 PM 4/10/2002 -0500, you wrote: > > >The majority of open source software is written by people who expect to >use > > >the software. Therefore, you have more occurances of developers actually > > >using their software, and performing their own bug testing. This, > > >unfortunately, doesn't happen in many large software shops. For example, ================================================ BRLUG - The Baton Rouge Linux User Group Visit http://www.brlug.net for more information. Send email to [EMAIL PROTECTED] to change your subscription information. ================================================
