Rtandrew Del Marcus's Reviews > Engineering Management for the Rest of Us
Engineering Management for the Rest of Us
by
by

Sarah Drasner puts the reader into her own experience by stating that the book is for engineers who are not necessarily born leaders and are forced to take leadership roles. She believes that management is still related to code, as without it, the latter produces no real outcome.
Managers must sacrifice themselves for the greater cause. In my POV and experience, this means that managers' jobs start two hours before and end two hours after, mainly because this job is interruption-driven to allow developers to have free-flow work.
She also shares insights on the importance of values in shaping team dynamics, where there lies a battle among a company's values, the leader's values, and each member's values. The company is the baby of the CEO vision, the team is a reflection of how the leader plans to achieve it, and it's in the best interest of the leader to structure the team "without someone else's idea". It's important to stay true to one's “self-vision� and someone else’s vision.
It's also important to stick together as a leadership team, be it to share failures and celebrate wins. This resonates with me because in my environment, everyone was a first-time leader, so having a shoulder I could count on alleviated the pain and loneliness, especially at the beginning where we had no idea, mentors, and no clear results to guide us.
Reflecting on these while I was building an engineering culture at DevTest, team dynamics was the most important product of my efforts and the least tangible element to measure.
Because of that, I can conclude that it's the manager's job to:
- Enable the team and shield them from bureaucratic processes
- Anticipate and provide conflict management
- Create an environment where everyone is comfortable and willing to work their asses off
- Provide the vision and strategic alignment
- Act as a protector in public and a mentor in private (it's always your mistake and never the team's; it's always the team wins and not yours)
Team dynamics is a combination of:
- Shared values
- Being comfortable to share ideas
- Being able to show vulnerability
- Criticize and take criticism
- Spirit of collaboration
- Being authentic to one’s self
Managers must sacrifice themselves for the greater cause. In my POV and experience, this means that managers' jobs start two hours before and end two hours after, mainly because this job is interruption-driven to allow developers to have free-flow work.
She also shares insights on the importance of values in shaping team dynamics, where there lies a battle among a company's values, the leader's values, and each member's values. The company is the baby of the CEO vision, the team is a reflection of how the leader plans to achieve it, and it's in the best interest of the leader to structure the team "without someone else's idea". It's important to stay true to one's “self-vision� and someone else’s vision.
It's also important to stick together as a leadership team, be it to share failures and celebrate wins. This resonates with me because in my environment, everyone was a first-time leader, so having a shoulder I could count on alleviated the pain and loneliness, especially at the beginning where we had no idea, mentors, and no clear results to guide us.
Reflecting on these while I was building an engineering culture at DevTest, team dynamics was the most important product of my efforts and the least tangible element to measure.
Because of that, I can conclude that it's the manager's job to:
- Enable the team and shield them from bureaucratic processes
- Anticipate and provide conflict management
- Create an environment where everyone is comfortable and willing to work their asses off
- Provide the vision and strategic alignment
- Act as a protector in public and a mentor in private (it's always your mistake and never the team's; it's always the team wins and not yours)
Team dynamics is a combination of:
- Shared values
- Being comfortable to share ideas
- Being able to show vulnerability
- Criticize and take criticism
- Spirit of collaboration
- Being authentic to one’s self
Sign into Å·±¦ÓéÀÖ to see if any of your friends have read
Engineering Management for the Rest of Us.
Sign In »
Reading Progress
December 10, 2024
– Shelved
December 10, 2024
– Shelved as:
to-read
Started Reading
April 7, 2025
–
Finished Reading