Best of Leadership — April 2024
- 1
- 2
Substack·2y10 Must-Reads for Engineering Leaders
This post features a list of 10 must-read books for engineering leaders. It covers various topics such as building a team that doesn't depend on you, removing controls and bureaucracy, extreme ownership, high output management, and the 5 dysfunctions of a team. The post also recommends newsletters written by engineering managers for further learning.
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
Community Picks·2y
Managing technical quality in a codebase.
Managing technical quality in a codebase requires engineers to prioritize quality, adopt best practices, and align technical vectors. It is important to address hot spots causing immediate problems, adopt practices known to improve quality, and identify leverage points that preserve quality over time. Measurement of codebase quality is crucial, and organizations can establish technical quality teams or quality programs to maintain and improve technical quality.
- 13
- 14
Hacker News·2y
Flow state: Why fragmented thinking is worse than any interruption
Developers need time and space to enter a flow state, but flow state can turn into an end in itself. Internal interruptions and fragmented thinking are the worst barriers to flow. To reduce fragmented thinking, create mindfulness and nudging practices, reduce tech debt, and make information accessible. Investing in laziness requires team-wide work and organization-wide investment.
- 15
Community Picks·2y
Unpopular Opinion: It’s harder than ever to be a good software engineer
Being a good software engineer is harder than ever due to the evolving tech market, increased competition, and high expectations. It requires focusing on value delivery, staying updated with trends, and making architectural decisions. However, it's important not to get caught up in hypes, prioritize bringing long-term value, and avoid stress and burnout. Individual dedication, company focus on delivering value, and a supportive culture can help improve software engineering.
- 16
Substack·2yPower of Blameless Culture in Software Engineering
Blameless culture in software engineering prioritizes learning and improvement over assigning blame for failures. It fosters innovation, encourages accountability, improves collaboration, and boosts morale and confidence. Tech leads can contribute to this culture by leading by example, celebrating learning, facilitating post-mortems, and addressing root causes of mistakes.
- 17
- 18
