Advertisement

Abstract

The general predicament is as old as programming itself: an application is malfunctioning and it’s your job to fix it. Naturally, the best person to fix an application is the original author. The majority of maintenance engineers, however, don’t have this distinction. Topically, their boss hands them a program that someone else wrote three years ago, and they have to start from the very bottom of the learning curve.

Keywords

Source Code Garbage Collector Maintenance Engineer Debug Process Software Configuration Management 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Katie Hafner, CYBERPUNK: Outlaws and Hackers on the Computer Frontier (Touchstone Books, 1995. ISBN: 0-684-81862-0)Google Scholar
  2. 3.
    Edward De Bono, Lateral Thinking: Creativity Step-by-Step (HarperCollins, 1990. ISBN: 0-060-90325-2)Google Scholar
  3. 4.
    Donald Knuth, The Art of Computer Programming, Volume 3: Sorting and Searching, Second Edition (Addison-Wesley, 1998. ISBN: 0-201-89685-0)Google Scholar
  4. 8.
    Crispen Cowen et al., “Automatic Detection and Prevention of Buffer-Overflow Attacks.” Paper presented at the 7th USENIX Security Symposium, San Antonio, TX, January 1998.Google Scholar
  5. 10.
    Richard Stallman et al, Debugging with GDB: The GNU Source-Level Debugger (Free Software Foundation, 2002. ISBN: 1-882-11488-4)Google Scholar
  6. 11.
    Dan Rollins, IBM-PC: 8088 MacRo Assembler Programming (MacMillan, 1985. ISBN: 0-024-03210-7)Google Scholar

Copyright information

© Bill Blunden 2012

Authors and Affiliations

  • Bill Blunden

There are no affiliations available

Personalised recommendations