The most interesting takeaway for me is this: [...] The best quality of a Design today is how well it can be undesigned [...] Aiming for design that's easy to

The most interesting takeaway for me is this: [...] The best quality of a Design today is how well it can be undesigned [...] Aiming for design that's easy to refactor and/or replace bolsters application longevity at the expense of code longevity. I like that. It's like the ecosystem longevity is achieved at the expense of the longevity of individual organisms... Now then, who has ideas, or best practices or even just anecdotes? I'm eager to hear those! For my part, I follow design philosophy that revolves around persistent data structures. My code is supposed to be just an accessory to the data. I don't think I'm explaining this well, it's just where I put all my focus on. Another principle is to try capturing users intent rather than the outcome of users actions. This way I can redo the code that detived outcome from actions and fix some the earlier erroneous behavior.