Code review is the manager’s job
Engineering Impact is a weekly newsletter that highlights trends in engineering leadership, productivity, culture, and scaling development teams.
This week features posts on: High Output Management, Productivity, Communication, Culture, and Distributed Teams.
HIGH OUTPUT MANAGEMENT
“The code review is the highest leverage point for improving an engineering team’s output.” John Barton, former VP of Engineering at 99designs, outlines why code review is such a high-value process, and explains how leaders should proactively manage it.
Gergely Orosz, Engineering Manager at Uber, collects the patterns he’s seen over a decade of shipping software in various environments and summarizes the core principles that he’s seen make or break projects.
“As a report, you could just blame your manager, or you could actually fix the situation yourself.” Here’s Osman Ahmen Osman, Head of Product Engineering at Quora, with an alternative approach for diagnosing and solving micro-management in your organization.
Prioritizing being “nice” as a leader can have a toxic effect on your culture. Claire Lew, CEO of Know Your Company, explains why “being nice” can become a crutch — and argues for making the distinction between ‘being nice’ and ‘being honest’ in your team.
“For all the reasons remote work as an individual came easily to me, remote leadership is hard.” Rick Banister, Designer at Automattic, elegantly describes his journey from IC to a leadership position — while working from afar.
Ben Thompson is a co-founder at GitPrime where he leads design and customer experience. He is a Y Combinator alumni, with a background in product design, branding, and UX design. Follow @thebent on Twitter.
Get Engineering Impact: the weekly newsletter for managers of software teams
Keep current with trends in engineering leadership, productivity, culture, and scaling development teams.