Living in your programming environment [pdf]
hpi.uni-potsdam.de
hpi.uni-potsdam.de
But unlike a Smalltalk environment, the things you were editing were (in metaphor at least) living narrative "world" objects like rooms, objects, characters, etc. meant to give a (text-based) "VR" aspect. And it was multiuser, so collaborative.
It's a compelling, though exotic, way of making things.
I'm attempting to defibrilate the whole thing here: https://github.com/rdaum/moor
The open nature of the environment led to data loss and corruption: crashes or forced restarts corrupted the Squeak image, faulty email synchronization scripts deleted server data, ad-hoc scripts sometimes created incomplete Person instances. The authors identified the need for transactions, backups, and crash recovery features. Storing all objects in memory limited scalability. And there is no mention of "performance" in the whole paper.
If only there was some decades old persistence implementation...
https://gemtalksystems.com/small-business/gsdevkit/
Oh!
> experienced programmer
So not actually an example of "knowledge workers themselves should ideally be able to quickly adapt the software tools."