Taylor Desseyn walks through the shift from senior engineer to leadership. Stop leaning on established patterns and build reference implementations instead. Start owning operational concerns: deployment, memory, CPU management.
Chapters
Give me 3 things people should be mindful of making that jump from senior to leadership. When you move beyond the senior engineering level, it's kind of like you stop working with handrails. You start like climbing up the mountain and you used to have handrails on both sides. You need to be able to start taking on bigger and bigger problems that take some thought. Additionally, as you move into these leadership roles, no longer do I want you to write good code and good tests and things like that. Can you write what I would call the reference implementation? What is the correct way to start with? What is it to write the code that is the perfect example of this is how it should start, this is how I should build my endpoints, this is how I should talk to a database, this is how I talk to a queue, that kind of thing. How do I deploy this so that I know how it's running and that it's managing its memory and its CPU correctly?