Introduction

The second part of "Dragons" is an example of effects described in the article http://home.pages.de/ Vit/ErrorLog_Dragons.html "The Software Dragons." If you hadn't read the first part, you may not understand some used terms.

This article doesn't describe new methods, powerful tools, fashionable programming languages or others things that can decrease the first three outcomes of your project, I'll describe here how decrease a dangerous part of the fourth outcome, your own Dragon of The Source Code. There are many papers full of good advises. This one is quite different. It tells you why these advises don't work.

To understand the Dragon of The Source Code you need to have some experience in the maintaining of the code written by others. You need to know that the time necessary for "small changes"

• may be much shorter,
• may be equivalent
• and may be much longer

than the time necessary to write the program anew.

If you haven't got such experience, you may not accept things I'll speak about.