Not a book, but here's a lengthy reply[0] to a thread that contains links to other replies to similar threads. You may skip the first part and go directly to the links at the bottom, as the first paragraphs addressed what lead to the learning and taking over without a transition period. The links are more for technical roles across the spectrum (individual contributor -- CXO). They explain how to leverage time, gain skills, align with a team, communicate with stakeholders at different technical depths and abstraction levels, institutionalize knowledge, build product, etc.
Comments
Not a book, but here's a lengthy reply[0] to a thread that contains links to other replies to similar threads. You may skip the first part and go directly to the links at the bottom, as the first paragraphs addressed what lead to the learning and taking over without a transition period. The links are more for technical roles across the spectrum (individual contributor -- CXO). They explain how to leverage time, gain skills, align with a team, communicate with stakeholders at different technical depths and abstraction levels, institutionalize knowledge, build product, etc.
- [0]: https://news.ycombinator.com/item?id=26182988