📎 Webclip
Science of happy developers: How to boost your engineering team's mojo
The article argues that teams usually look in the wrong place when they try to restore developer mojo. New languages, tools, platforms, and processes do not solve the problem on their own. What matters more is the manager’s relationship with each developer.
Research cited in the piece says job performance and satisfaction are shaped by that relationship, and it describes how in-groups and out-groups form around it. To improve those relationships, the article recommends hiring for soft skills and keeping weekly one-on-one meetings for trust, feedback, and candid two-way communication.
Reading notes#
- Developer happiness is tied more to the manager relationship than to changes in technology or process.
- Research on LMX theory is used to explain why the quality of the manager-developer relationship affects satisfaction, productivity, motivation, and turnover.
- Managers naturally end up with in-groups and out-groups, and those groups differ in trust, autonomy, advancement, and performance.
- The article says managers should notice how those groups form and invest in stronger relationships across the whole team.
- It recommends hiring programmers who value relationships and have the soft skills to participate in them.
- It presents weekly one-on-one meetings as the main practice for building trust, sharing feedback, discussing impediments, and hearing candid input from developers.
- The article warns that canceling one-on-ones weakens the relationship, and that an open-door policy is not an effective substitute.
- It closes by saying developers usually leave managers, not technology, and that good relationships, steady time investment, and direct feedback are what restore team mojo.
