Indeed, the analogy is rough and probably reveals that I am not a programmer by trade. As with all analogies, one hopes that others can lift them into slight ab

Indeed, the analogy is rough and probably reveals that I am not a programmer by trade. As with all analogies, one hopes that others can lift them into slight abstraction in order to find the meaning and reach a similar conclusion or line of thought at least. Even if I could be helped in improving it, analogies are virtually never airtight– in this case comparing a physical park to software is not without difficulty. Sadly I can't think of any prankware that would really get the message across here. Edit: Re-reading your comment I might have missed a few parts so I'll reply back while waiting for paint to dry (fun day). I wasn't trying to equate the two systems or their intricacies and behavior. Rather, we are given some system with rules which govern what we expect it to "be". (I could say do, but consider this the "state" of the system; if it is code, it is not executing but just lines of code in files.) When that system is changed in a way we do not expect by an action that we had prior expectations for, we generally try to revert that action. You are responsible for your system, so you can do what you like. Parks and Rec is responsible for this park, and all of its users and rightly intends to remove this unexpected modification, regardless of its origin or meaning. I'm just realizing what a missed opportunity to be hip it was– when you let a friend provision your vagrant images with unknown docker containers with [insert unexpected behavior] just before distributing it to thousands of users... (The potential danger of the thing would be a side-effect though so this one's not so good either. I tried!)