The hottest Engineering Management Substack posts right now

And their main takeaways
Category
Top Technology Topics

Being an Engineering Manager at Meta

Leading Developers • 100 implied HN points • 14 Jan 25
🕹 Technology Software Development Engineering Management Company Culture Leadership Career development
  1. At Meta, managers are there to support their engineers, who have the freedom to choose their projects and set goals. This leads to a culture where trust and autonomy help engineers excel.
  2. Managers at Meta are evaluated based on the impact of their team and how they help individual contributors grow. It's important for managers to realize their role in coaching and supporting their engineers, rather than taking credit for their success.
  3. Meta encourages a fast-paced environment where developers can easily set up their work and start contributing quickly. This focus on efficiency comes from long-term investments in tools that make working faster and smoother.

Measuring developer productivity: A clear-eyed view

Engineering Enablement • 21 implied HN points • 05 Feb 25
🕹 Technology Software Development Developer Experience Productivity Metrics Engineering Management Data Analysis
  1. Metrics for developers should help improve their work experience, not just measure their output. Goodhart's Law reminds us that once metrics are tied to rewards, they can become misleading.
  2. Developer experience is more about effectiveness than happiness. Measuring how developers feel needs to focus on the frustrations they face, and not just on making them comfortable.
  3. Using benchmarks is important but context is key. Just like medical tests, numbers need interpretation to make sense; comparing different teams requires understanding their unique challenges.

Engineering Management: Dealing with the Broken Window effect, understanding Resistance and Objections to Quality

🔮 Crafting Tech Teams • 79 implied HN points • 14 Mar 24
🕹 Technology Engineering Management Technical Debt Change Management Resistance
  1. The bar for quality is defined by influential leaders and can evolve over time based on business needs.
  2. Stakeholders may request changes to either increase or decrease quality based on signals like bugs, morale, and process burden.
  3. Resistance should be considered when changes to quality are ignored to avoid negative impacts.

Quality Engineering Basics: Incident Reports

QUALITY BOSS • 39 implied HN points • 05 Apr 24
🕹 Technology Quality Engineering Process Improvement Software Development Engineering Management
  1. Incident reports help us learn from mistakes without blaming anyone. By understanding what went wrong, we can improve processes and avoid future issues.
  2. Writing incident reports takes time but leads to fewer problems later. They keep everyone informed and help prioritize important improvements.
  3. To make incident reports effective, clear criteria and responsibility are needed. It's important to track action items so that lessons learned actually lead to real changes.
Get a weekly roundup of the best Substack posts, by hacker news affinity: