Owl versus Parrot

Owl or Parrot?

We originally and perhaps still think of our systems as environments that parrot back what we tell them. Indeed, this may be the best way to think of them, because in the ordinary sense of the words systems neither "think" nor "learn."

In many respects, systems that have to "comply" must indeed be faithful parrots. The system that is reporting financial results has to "parrot" back inputs again and again, with great consistency even though the individual outputs have varying specifications and purposes. Similarly "validated" systems used by pharmaceutical companies need to function as trustworthy parrots.

On the other hand, we have to deal with the reality that many of our systems are independently collecting masses of data from various sorts of sensors. Such systems perform various operations to that data - e.g., regulating its "fidelity" in terms of, say, bits per image - and with that data - where to store it, whether to distribute it, etc. Given that such a system sits on top of what may be critical, huge data feeds, it in many respects becomes an "owl" - a source of "truth" telling you things that, for better or worse, must be trusted. As we deploy thousands of cameras or other sensors, these systems become an important part of our working lives and our personal well-being.

The fundamental limits pertain - neither the Parrot nor the Owl system can "think" or "learn," but they can mimic both thinking and learning in situations in which we have no choice but to listen. Thinking about the "epistemology" of both "parrot" and "owl" systems is therefore highly necessary.


Fulton Wilcox
Colts Neck Solutions LLC
www.coltsnecksolutions.com