Unlike the reason developers avoid managers, a current EM explains the fun of solving organizational problems(mtx2s.hatenablog.com)
Writing language: KoreanRead in the original language
Plain summary
- An engineering manager (EM) is a manager who leads a development team. The author says many developers probably see managers only in terms of approvals, meetings, coordination, responsibility and pressure, and admits that they themselves once turned down an offer to become a manager.
- The author argues that a manager is not a role about managing people only. It is a role of solving organizational problems so that the team can perform well, and the author sees the process of finding problems, understanding the structure and pinpointing the real cause as similar to engineering.
- As an example, the author describes investigating why team A often had to coordinate with team B. They found that the code owned by the two teams was tightly entangled, and after it was loosened, team A could develop without coordination.
- The author recommends that an EM of a single team act as a playing manager who also develops directly. The reason is to build technical judgment, but the author also admits that doing both is a heavy burden and that development skills grow more slowly.
Editorial opinion
O: For a developer hesitating over a manager offer, the suggestion is to pick one task that keeps requiring coordination between teams and write down whether it is an organizational problem or a code coupling problem.
X: Doing both is the author's opinion, and the author also admits that a player-manager role is a heavy burden and slows the growth of hands-on skills, so how much of it to take on should be weighed against the organization's situation.
Writing language: Korean
Found on
はてなブックマーク テクノロジー ↗ / Published by source
Have you run into something like this? Tell us in a line or two what you did. You do not need to know the product.