@article{SteinertCassouHirschfeld2013,
  author    = {Steinert, Bastian and Cassou, Damien and Hirschfeld, Robert},
  title     = {CoExist overcoming aversion to change preserving immediate access to source code and run-time information of previous development states},
  series = {ACM SIGPLAN notices},
  volume    = {48},
  journal   = {ACM SIGPLAN notices},
  number    = {2},
  publisher = {Association for Computing Machinery},
  address   = {New York},
  issn      = {0362-1340},
  doi       = {10.1145/2480360.2384591},
  pages     = {107 -- 117},
  year      = {2013},
  abstract  = {Programmers make many changes to the program to eventually find a good solution for a given task. In this course of change, every intermediate development state can of value, when, for example, a promising ideas suddenly turn out inappropriate or the interplay of objects turns out more complex than initially expected before making changes. Programmers would benefit from tool support that provides immediate access to source code and run-time of previous development states of interest. We present IDE extensions, implemented for Squeak/Smalltalk, to preserve, retrieve, and work with this information. With such tool support, programmers can work without worries because they can rely on tools that help them with whatever their explorations will reveal. They no longer have to follow certain best practices only to avoid undesired consequences of changing code.},
  language  = {en}
}
@article{SteinertHirschfeld2012,
  author    = {Steinert, Bastian and Hirschfeld, Robert},
  title     = {Applying design knowledge to programming},
  year      = {2012},
  language  = {en}
}
@article{HirschfeldSteinertLincke2011,
  author    = {Hirschfeld, Robert and Steinert, Bastian and Lincke, Jens},
  title     = {Agile software development in virtual collaboration environments},
  isbn      = {978-3-642-13756-3},
  year      = {2011},
  language  = {en}
}
@article{WeiherHirschfeld2014,
  author    = {Weiher, Marcel and Hirschfeld, Robert},
  title     = {Polymorphic identifiers: uniform resource access in objective-smalltalk},
  series = {ACM SIGPLAN notices},
  volume    = {49},
  journal   = {ACM SIGPLAN notices},
  number    = {2},
  publisher = {Association for Computing Machinery},
  address   = {New York},
  issn      = {0362-1340},
  doi       = {10.1145/2508168.2508169},
  pages     = {61 -- 71},
  year      = {2014},
  abstract  = {In object-oriented programming, polymorphic dispatch of operations decouples clients from specific providers of services and allows implementations to be modified or substituted without affecting clients. The Uniform Access Principle (UAP) tries to extend these qualities to resource access by demanding that access to state be indistinguishable from access to operations. Despite language features supporting the UAP, the overall goal of substitutability has not been achieved for either alternative resources such as keyed storage, files or web pages, or for alternate access mechanisms: specific kinds of resources are bound to specific access mechanisms and vice versa. Changing storage or access patterns either requires changes to both clients and service providers and trying to maintain the UAP imposes significant penalties in terms of code-duplication and/or performance overhead. We propose introducing first class identifiers as polymorphic names for storage locations to solve these problems. With these Polymorphic Identifiers, we show that we can provide uniform access to a wide variety of resource types as well as storage and access mechanisms, whether parametrized or direct, without affecting client code, without causing code duplication or significant performance penalties.},
  language  = {en}
}