More interesting is when some people work with the code, but don't touch the Dragon. They may know dangerous places and don't enter into. They may even become Dragon's servants. They cover up internal errors by ``protection code'' to hide visible effects of failures by program runs. The software is seemed to be good for use and the developers do not need to go into Dragon's house.
At a certain moment the amount of errors makes this game impossible. The developers are forced to change holy texts. With the whole power meets them the Dragon in the wilderness of ancient errors, patches, and patches of patches. The first step into forbidden zone may kill "working program".
The Dragon of The Source Code may wait his historic moment many years and decades. For instance until new millennium.