Skip to main content

Preventative Medicine

  • Chapter
  • 862 Accesses

Abstract

The role of the maintenance engineer is to exorcise the evil spirits that dwell in legacy software. Day and night, maintenance engineers are beset upon, and spited, as they forge a lonely path through the corporate landscape. Every day, they face the challenge of

  • Repairing bugs

  • Improving performance

The first four chapters of this book are devoted to looking at the first task. The final two chapters of this book deal with the second task.

This is a preview of subscription content, log in via an institution.

Buying options

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   29.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   39.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Eric S. Raymond, ed., The New Hacker’s Dictionary, Third Edition (MIT Press, 1996. ISBN: 0-262-68092-0)

    Google Scholar 

  2. William J. Brown et al., AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis (John Wiley & Sons, 1998. ISBN: 0-471-19713-0)

    Google Scholar 

  3. Rebecca Sykes, “AOL buys Netscape, joins Sun in Java Deal,” IDG News Service, November 24,1998

    Google Scholar 

  4. Walter Oney, Programming the Microsoft Windows Driver Model, Second Edition (Microsoft Press, 2002. ISBN: 0-7356-1803-8)

    Google Scholar 

  5. Charles Mann, “Why Software Is So Bad,” Technology Review, June 17,2002

    Google Scholar 

  6. Ibid.

    Google Scholar 

  7. Introduction to Assembly Language Programming (Springer Verlag, 1998. ISBN: 0-387-98530-1)

    Google Scholar 

  8. Matt Nicholson, “Understanding Software Components,“ DNJ Online, September 1997

    Google Scholar 

  9. Duncan Mackenzie, “Developing Custom Windows Controls Using Visual Basic.NET,” MSDN, May 2002

    Google Scholar 

  10. George A. Miller, “The Magical Number Seven, Plus or Minus TWo,“ Psychological Review, 1956, vol. 63, pp. 81–97

    Article  Google Scholar 

  11. Frederick P. Brooks Jr., The Mythical Man-Month (Addison-Wesley, 1995. ISBN: 0-201-83595-9)

    Google Scholar 

  12. Thomas Gutschmidt, “Securing Java Code: Part 4,” developer.com, June 6, 2001

    Google Scholar 

  13. John Robbins, Debugging Applications (Microsoft Press, 2000. ISBN: 0-7356-0886-5)

    Google Scholar 

Download references

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2012 Bill Blunden

About this chapter

Cite this chapter

Blunden, B. (2012). Preventative Medicine. In: Software Exorcism: A Handbook for Debugging and Optimizing Legacy Code. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-5108-8_1

Download citation

Publish with us

Policies and ethics