[kangaroo5383]

Great read, thank you for posting that! There's an interesting shift towards empathy in programming that I think will make better software. The empathy to ask - what is the easiest for the user, what are the expected actions and expected results from the user's point of view, etc. This same approach can be used in actual software design as well - treat each components / class / API as a person with motivations and goals, figuring out what's the least amount of info this person needs, best way to get to their goal etc. I've found that way of thinking yields cleaner design overall, and is easier to communicate to others. This method of approaching problems should be encouraged, heck, if not demanded, from all!