tl;dr: Risk tolerance defines leaders. Those with a low tolerance become bureaucrats - glamorous titles, big paychecks, scarred from past experiences. Others "embrace death," seeing it to be their duty to "protect and empower."
tl;dr: "Creates clarity on how you work — what you value, how you look at problems, what your blind spots or areas of growth are, and how to build trust with you." Julie recommends writing your own guide to give to managers and teammates, providing examples.
tl;dr: (1) Work directly with smart people that challenge you intellectually. (2) Stick with projects through multiple cycles so you "develop an intuition about what really matters when you code." (3) Understand the breadth vs depth tradeoff. (4) Patience.
tl;dr: Uduak guides through 13 things he's learned before, during and after interviews, such as how to handle introductory phone and technical phone calls, what to do when you’re stuck on a problem in the interview, and more.
tl;dr: (1) Value contributions to documentation just as much as code contributions. (2) Put documentation and code in the same project repo. (3) Make documentation a requirement for a merge or release milestone, and more.