This is how I would imagine the &#x27;fierce shark&#x27; being programmed:<p>1) The &quot;fierce&quot; plugin is installed and immediately run. It is targeted on the shark sprite.<p>2) &quot;Fierce&quot; is an evolutionary algorithm. It will create several hundred generations of a shark, mutating the shark sprite in some small way. The shark&#x27;s fitness is based on how &#x27;scary&#x27; the shark is, and the &#x27;scariness&#x27; of the shark is calculated based on a dataset compiled by children that rated how scary colored pictures were from a scale of 1 to 10. The evolutionary algorithm&#x27;s goal is to maximize the fitness of the shark.<p>3) The final shark (with the highest fitness) is outputted to the user. It will look very similar to a normal shark, with some minor variations in color to increase the scariness of the shark.<p>What these people are doing is not impossible. However, the potential for so-called &quot;leaky abstractions&quot;[0] messing up the development process is very high. Programmers will likely be necessary, if only to ensure the abstractions are functioning well enough for non-programmers to use.<p>[0]<a href="http:&#x2F;&#x2F;www.joelonsoftware.com&#x2F;articles&#x2F;LeakyAbstractions.html" rel="nofollow">http:&#x2F;&#x2F;www.joelonsoftware.com&#x2F;articles&#x2F;LeakyAbstractions.htm...</a>