When engaging in exploratory programming, the activities of exploring, understanding, implementing, and using objects of a particular domain should ideally be tightly interwoven to allow for short feedback cycles and continuous progress toward desired levels of comprehension and knowledge. However, when working with plain data objects using state-of-the-art development tools, programmers often have to resort to a more sequential work ow in which they first need to understand the model, then implement it, and only afterwards can start using and exploring it.

In this proposal, we want to illustrate how our exploration workspace tool allows for interleaving these activities to better support the exploration of objects programmers are not fully acquainted with. We achieve this by trying to tolerate deviations of the protocol assumed from the one actually provided by the objects the programmers wish to interact with. For that, we strive for non-intrusive tool support that helps to semi-automatically build up the vocabulary preferred in interactions. We also suggest to consolidate both domain object implementations and exploration scripts once learning progressed.

In a demonstration, we will illustrate various resolution strategies applied during the implementation of a geographical map showing social media posts and photos.