I think there are two different things happening here, which are not quite pinpointed. We have to work for both, but they are different kinds of work. With phy

I think there are two different things happening here, which are not quite pinpointed. We have to work for both, but they are different kinds of work. With physical things, you want them to keep doing the same thing, but they degrade themselves. With software, it just stays being the same, but you want to keep changing what you do with it. Are there not rather different kinds of knowledge-work demanded there? With keeping things the same, you have a basically closed-ended aim -- you just gather more knowledge and you have it cornered. But with changing things everything is always open-ended -- what you will need to know seems basically unpredictable. That is why there is subtle mistake in trying to design software to be adaptable. It is a contradiction. Design is using knowledge to make something, but the whole point about the kind of change we are facing here is that it is basically unpredictable. You cannot design for the future, because you cannot design for what you do not know. You just have to adapt when it arrives. Or something.