1. Strive to understand how your work fits in with the overall organization. Code by itself is a liability; make sure you know how your code is used to provide

1. Strive to understand how your work fits in with the overall organization. Code by itself is a liability; make sure you know how your code is used to provide value to the organization. 2. When appropriate, ask your manager for more context into areas that aren't readily visible to you. What metrics do they care about? What metrics do their boss, their boss' boss... care about? 3. Provide frequent feedback, both affirmative and critical. When providing criticism, do so constructively, and always have ideas for possible solutions. Also remember that there may be other factors that you're not aware of (see point #2). Explicitly acknowledge that you're not criticizing any individual, and admit that you don't have all of the answers. Adapt your perspective fluidly when new information comes in. 4. Make sure your efforts are in line with the direction of your team, your division, the organization, and the industry. 5. Assume positive intent. 6. Be mindful of how your actions are perceived outside of your immediate team. Optics are important. 7. Make your manager's peers envious of the team that [s]he has assembled.