1. 22
  1. 5

    This advice, if I expand it would be: “Always make your best to you put yourself into the shoes of the person you are communicating with”.

    As developers, when we “communicate with computers”, we do not need to put ourselves into its shoes. (I know, understanding interrupt handlers and register allocation helps a lot, but this not the same analogy :-)).

    For myself, I takes me time to switch… After I am deep hours or days into programming, or studying something hard – I find that I need to make a conscious effort to get out of that, and my mind needs to stop ‘examining’ every word, every interaction for ‘how correct and precise’ it is’, ‘what category of things that word belongs to’, and what ‘long term consequences’ of something are. :-)