Pattern of Perception

Once again, here we are facing the often dreaded situation. We know enough of what we want to tell if an implementation suits our requirements, but we have not written a single line of code yet. What do we do first? At this critical point, it will be most valuable to assess what could be the benefit of each of the actions available to us.

The pattern of perception consists of a player that has an interface with an incoming and outbound pipe, a set of eyes, a Strategy which produces objectives, and a set of hands. Apparently, there is not a lot to abstract here because each of these objects has a distinct, well defined responsibility.

DOT FROM lambda-browsing