The Perfect Virus principle #19: Simultaneity

As indicated in my post of Monday, 11/22/2010, I am extrapolating Jeff Walker's Principles for the Perfect Application into a discussion of The Perfect Virus. Since Jeff's monograph on the subject did not anticipate stealth or suicide mechanisms, any errors or lapses into stupidity are solely my additions and should not reflect poorly on what I consider to be the biggest single contribution to software application design since the invention of computers. And Jeff, thanks for giving me permission to do surgery on your baby.

THE PRINCIPLE OF SIMULTANEITY: The Perfect Virus spawns applets capable of doing many things at once. And since it obeys principle #5 (Seamless Migration), it can be multi-threaded not only on the same machine but on different machines, architectures, and operating systems as well. This is also beneficial to Stealth (principle #14), in that distributing MIPS and machine cycles can reduce the chance of getting detected through abnormal clock usage. Naturally, you'll have to piggyback on legitimate network packets or the not-so-perfect virus will give itself away through network traffic anomalies.


When The Perfect Virus goes into attack mode, Simultaneity will give you the option of either setting off all the alarms at once, or triaging the attack by mission priority parameters dictated via the Prosumption (principle #11) dashboard. 


Another advantage of Simultaneity is the natural opportunity to use Native Implementation (principle #9) and No Common Denominator (principle #10) to use either multi-core processor architectures or massively parallel features of the target system.