Nice article. Just a good reminder to think about the 'unwritten objects' which emerge out of one's code and to compose those sensibly as well. Kinda reminds m

Nice article. Just a good reminder to think about the 'unwritten objects' which emerge out of one's code and to compose those sensibly as well. Kinda reminds me of contracts -- it's not what's written in the contract that matters, but rather what's not written. Teasing out the natural consequences of the interaction between the stated and unstated is a requirement of being a good lawyer (well, as far as contracts are concerned). Perhaps there's an analogy for good programmers?