1. Second-Order Thinking
Considering the downstream consequences of your actions by asking 'and then what?', such as proactively interviewing while happily employed to mitigate future layoff risks.
Hear it at 0:03 →Engineering video
0:47 · 18 August 2023
How To Improve Your Thinking As A Developer
Key concepts in this video:
Transcript
senior developer mental models 7 out of 10. second order thinking software developers can for sure benefit from this concept which has been described first by Howard marks an American writer an investor it states that you should always try to think about the consequences second order of your actions before you take them it means asking yourself and then what for example if you're happy at your development job or your company faces Financial issues they might let you go so you should go to the market now and interview to be prepared this means getting over your fear of interviewing first and mastering your skills second
you can tell yourself everything will be fine and do nothing but second way they thinking will make you realize that that is the most risky option high performance always consider the second order consequences of their behavior and act upon