Bridging the Gap Between Junior and Senior Engineers
Engineering Impact is a weekly newsletter that highlights trends in engineering leadership, productivity, culture, and scaling development teams.
This week features posts on: Career, Scalability, Prioritization, Process, Responsibilities.
In a thoughtful response to a question posted in /r/cscareerquestions, Jacob Comer offers a list of areas that typically distinguish senior engineers from those with less experience — effectively offering junior engineers with a path for growth.
Matt Klein, Engineer at Lyft, argues against using a monorepo. Why? He says: “At scale, a monorepo must solve every problem that a ‘polyrepo’ must solve, with the downside of encouraging tight coupling, and the additional herculean effort of tackling VCS scalability.”
Julie Zhou, VP of Product Design at Facebook, reframes the discussion around “The Tradeoff Between Quality and Time,” and offers a more productive conversation to have next time you find yourself in this situation.
“Even without being paged, being on call creates anxiety,” says Brian Scanlan, Engineering Manager at Intercom. Here’s the history of on-call at Intercom, and how that process has evolved over time.
The role an Engineering Manager can be interpreted in vastly different ways depending on the company. Here, David Ives, Engineering Manager at Pusher, attempts to bring clarity about the role by comparing it to the roles of the VPE and CTO. He says, “The EM is the interface between strategy and delivery.”
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.