Each article offers practical insights that can help leaders foster a healthier, more supportive environment for engineers. By reevaluating and improving these aspects, organizations can ensure their on-call practices not only support system stability but also contribute to a positive workplace culture.

This time, we explore various dimensions of on-call practices—from compensation and runbook creation to sustainable software development.

1. How to Write Good Runbooks

   This article emphasizes the importance of well-crafted runbooks in incident management. It offers practical advice on making runbooks actionable, reducing the stress and uncertainty that often accompany on-call situations.

2. Navigating On-Call Compensation in the Tech Industry in 2023

   Discusses the evolving landscape of on-call compensation, providing insights into how fair and motivating compensation practices are essential for maintaining team morale and performance.

3. Incident Metrics Tell You Nothing About Reliability by Dan Slimmon

   Dan assesses (critically) the effectiveness of using incident metrics to gauge system reliability, proposing a more nuanced approach to understanding what these metrics truly indicate about our systems.

4. Oncall and Sustainable Software Development

   This piece links effective on-call practices with sustainable software development, suggesting ways to align on-call duties with a broader commitment to developer health and software quality.

5. Project Star: Streamlining Our On-Call Process

   A case study from LinkedIn detailing how they refined their on-call process to boost developer satisfaction and productivity, providing a practical example of successful on-call management.

Understanding how to enhance observability and have meaningful alerts is important for proactive system management and incident response.

Featured Articles

1. What Makes a Good Alert? by Dan Slimmon

   Dan delves into the essentials of what constitutes a good alert, emphasizing the importance of alerts being actionable and informative. This piece is a great starting point for anyone looking to refine their alerting strategy to minimize noise and maximize relevance.

   

2. No Observability Without Theory by Dan Slimmon

   This article pushes the idea that effective observability requires a solid theoretical framework. Without it, data collection might lead to more confusion than clarity, highlighting the need for a well-thought-out approach to observability tools.

   

3. On-Call by Cindy Sridharan

   Exploring the personal and systemic impacts of on-call duties, Sridharan discusses how these responsibilities influence system design and employee wellbeing, providing insights into balancing these aspects effectively.

With this edition, I wanted to focus a little on the critical aspects of system alerts and observability, offering insights into how we can better design our monitoring systems and alerts to be both informative and actionable. From theoretical frameworks to practical tips on alert design, these articles provide valuable guidelines for enhancing system reliability and effectiveness.

As leaders, incorporating these principles can lead to more resilient systems and more prepared teams.

These are interesting reads for you and for your team to decide how and in what direction do you want to build your documentation culture.

1. Technical Writing Courses for Engineers by Google Developers

   • Kickstart your journey with Google's technical writing courses for engineers. It's your first step towards documentation that speaks volumes.

2. Design Docs at Google by Malte Ubl

   • Writing great design documents is about making complex projects a little less daunting.

3. Writing Practices and Culture at HashiCorp

   • See how HashiCorp's ethos of clear communication is embedded into their DNA, making documentation a pillar of their engineering culture. For them, it's more than just writing—it's about forging connections.

4. Docs for Developers: An Engineer’s Field Guide to Technical Writing

   • Dive into this comprehensive guide for tips that turn the chore of documentation into a charm.

5. Documentation System

   • Discover a system that sorts your docs into neat categories, making them as easy to find as they are to follow. It's about giving every piece of writing its rightful place.

This week, challenge yourself to view documentation not as a duty but as an opportunity to distill complexity into clarity.

Catch you in the next edition!

This week, we delve into a critical, yet often overlooked, skill in the tech industry: writing.

Whether it's documenting code, drafting proposals, or sharing insights through blogging, writing is a fundamental tool for communication, learning, and influence in engineering.

1. "Writing Is Thinking” by Andrew Bosworth

   • Boz delves into how writing is not just a method of communication but a way to sharpen your thinking. An article I personally come back to multiple times for its insights on how articulating your thoughts can lead to clearer decision-making and stronger problem-solving skills.

2. "Undervalued Software Engineering Skills: Writing Well" by Gergely Orosz

   • Gergely offers insights into the iterative process of writing well, emphasizing the importance of practice, feedback, and improvement. This article sheds light on how honing your writing skills can significantly enhance your communication, ultimately elevating your team's performance.

3. "Write about what you learn. It pushes you to understand topics better" by Addy Osmani

   • Addy advocates for writing as a learning tool, sharing how the act of writing can consolidate knowledge and foster innovation. He illustrates with personal anecdotes how explaining concepts in writing has solidified his own understanding and expertise in complex subjects.

4. "Some tactics for writing in public" by Julia Evans

   • Julia shares her personal journey and strategies for writing in public spaces, tackling the fears that often hold many back. Her insights are invaluable for anyone looking to influence and contribute to the broader tech community. Julia emphasizes the role of vulnerability in growth, encouraging engineers to share their learning process with the world.

5. "Writing is Thinking" by Sally Kerrigan

   • In this brilliant read Sally explores the intrinsic link between writing and thinking, arguing that effective writing can lead to more precise solutions. She extends the conversation to how writing facilitates a deeper understanding of challenges, fostering a culture of clarity.

   ---

The power of writing extends far beyond mere documentation or just a response; it is a medium through which we can clarify our thoughts, share our knowledge, and connect with others on a meaningful level.

This week, I challenge you to reflect on your writing practices and consider how you might leverage writing to enhance your engineering and leadership journey.

Until next time!

In this issue, we dive into goal setting and personal development. These are not just buzzwords; they're the essence of our journey as engineers and leaders.

1. The Goal Setting Conundrum by Nadyne Richmond

   Nadyne explores the very real challenges in setting career goals. The post calls out various obstacles such as analysis paralysis, uncertainty about the future, impostor syndrome, and skepticism about the goal-setting process. And offers potential ways out.

   Key Takeaways:

   1. Strategies are provided to tackle each obstacle, emphasizing the creation of SMART goals.

   2. Importance of establishing an accountability structure to track progress.

2. How Tracking and Streaks Help You Establish Habits and Reach Your Goals by Ashley Janssen

   Janssen explains the effectiveness of daily tracking and maintaining streaks in building habits and achieving goals. She highlights the psychological benefits of marking tasks as complete and the importance of self-reflection in tracking.

   Key Takeaways:

   1. Daily tracking supports consistent practice and habit formation.

   2. Tracking aids in prioritizing and making informed decisions, and involves identifying what's important to the individual.

3. Personal Growth Targets for Senior Leaders by Aviv Ben-Yosef

   Ben-Yosef emphasizes the necessity of personal growth for senior leaders, suggesting setting new targets every 2-3 months. The article covers areas like communication, self-productivity, leadership skills, and team shaping.

   Key Takeaways:

   1. Leaders need to focus on communication skills, effective decision-making, and strategy development.

   2. Team shaping involves providing autonomy, coaching managers, and setting a positive culture.

4. Aligning Dreams And Goals by Tom Sommer
   Tom has created a simple guide for managers on goal setting, considering individual career stages and ambitions. It categorizes goals into three types: The Aligned Goal, The Career Move, and The Dream, each requiring a different approach.

   
   Key Takeaways:

   1. The importance of individualized goal setting in management.

   2. Balancing an employee's career aspirations with team success and finding common skills between their current role and future aspirations.

Tools:

• YearCompass: The Booklet That Helps Close Your Year and Plan the Next One

  ---

  In this edition, we've read about the nuances of goal setting and personal growth. It’s a reminder that our professional pursuits are deeply intertwined with our personal journeys. Here's to growing together in this ever-changing landscape of tech.

This edition is all about the art and science (and sometimes, madness) of making accurate estimations. Whether you're leading a team or working as a senior engineer, understanding how to estimate effectively is important.

1. Four Kinds of Dates by Rich Lafferty (Estimated Reading Time: 6 mins)

   Key Learning: Lafferty introduces a model of four kinds of dates—estimates, targets, soft deadlines, and hard deadlines—to help clarify communication and avoid misunderstandings around project timelines.​

2. Yes, Virginia, You Can Estimate That by Camille Fournier (Estimated Reading Time: 7 mins)

   Key Learning: Fournier demystifies the estimation process, emphasizing that successful estimations aim to be within a 20% margin of the goal and discusses the importance of understanding scope and requirements for accurate estimations.

3. LeadingIn Tech #6: Estimated Time of Arrival Panic by Roberto Ansuini (Estimated Reading Time: 5 mins)

   Key Learning: This article highlights the importance of not rushing to give a first date, avoiding overly optimistic estimates, and making assumptions explicit. It also stresses the value of breaking down projects into atomic parts for better estimation accuracy​.

4. Estimated Time != Calendar Time by Leeor Engel (Estimated Reading Time: 8 mins)

   Key Learning: Engel discusses the difference between estimated time and calendar time, emphasizing the importance of accounting for engineering capacity, organizational specifics, and project start dates in estimations.

In conclusion, in this week's edition, I wanted to touch a critical skill in engineering leadership: the art of making accurate estimations. The trick is to remember that estimations are not just about hitting deadlines; they are about setting realistic expectations, managing resources efficiently, and maintaining team morale.

As you reflect on these readings, ask yourself:

• How can you apply these principles to your current projects?

• Are there any estimation practices in your team that could benefit from these insights?

• How can you improve communication around timelines and expectations?

Your feedback and suggestions for future editions are always appreciated. Feel free to come and say hi!

This week's edition is written for Senior Engineers and Engineering Leaders with a focus on the skills required beyond coding proficiency. Whether you are leading a team or attempting to enhance your personal development, these articles will hopefully provide insights into the broader skills necessary for senior engineering roles.

1. An Incomplete List of Skills Senior Engineers Need, Beyond Coding by Camille Fournier (Estimated Reading Time: 6 mins)

   Key Learning: Senior Engineers require a diverse skill set that is beyond coding. From running effective meetings and mentoring peers to influencing cross-team projects and handling non-technical stakeholder discussions, Fournier lays out essential skills that are often overlooked​.

2. How Do Individual Contributors Get Stuck? by Camille Fournier (Estimated Reading Time: 5 mins)

   Key Learning: Understanding the common pitfalls that hinder the progress of individual contributors is crucial. Fournier discusses scenarios like overthinking solutions, getting sidetracked by helping others, and struggling with project planning, offering insights on how to navigate these challenges​.

3. On Being a Senior Engineer by John Allspaw (Estimated Reading Time: 8 mins):

   Key Learning: Seniority in engineering isn't just about technical ability; it encompasses maturity, empathy, and awareness of cognitive biases. This article emphasizes the importance of understanding trade-offs, avoiding CYAE (Cover Your Ass Engineering), and being empathetic towards different stakeholders in a project​.

4. Start Right Before You Get Eaten by the Bear by Wes Kao (Estimated Reading Time: 4 mins)

   Key Learning: Effective communication is the key in senior roles. This piece encourages professionals to cut the fluff and be concise, focusing on the essence of the message to enhance clarity and efficiency​.

As you lead or progress in your role as a Senior Engineer, it is important to refine these broader skills that greatly contribute to your effectiveness and influence. The readings for this week aim to emphasize skills that go beyond technical expertise.

I hope that these articles offer you valuable insights. Your feedback and suggestions for future editions are always appreciated.

Feel free to come and say hi!

Hey Engineering Leaders!

If the quote above from Camille Fournier strikes a chord with you, and you struggle with something known as “Other People Problems Syndrome!” — hop in with me, for this edition. This time, we explore the subtle yet crucial aspects of leadership in engineering, focusing on the core responsibilities and the unseen challenges that accompany them.

1. Other People's Problems (OPP): A Leadership Conundrum by Camille Fournier (Estimated Reading Time: 8 mins): Fournier discusses the challenge of balancing involvement in team issues with empowering team autonomy. A crucial read for understanding when to intervene and when to step back.

   1. 

      1. Key tip: Print that graph out, and read that again, and again.

2. The Significance of 'Glue Work' in Engineering by Tanya Reilly (Estimated Reading Time: 7 mins): Tanya sheds light on 'glue work', those essential yet often unrecognized tasks that keep teams and projects cohesive. A must-read for appreciating and acknowledging it, and figuring out how to navigate the challenges around the same.

3. Staying True to Your Core Role: Charity Majors' Insight by Charity Majors (Estimated Reading Time: 6 mins): Key Learning: Focusing on your primary job responsibilities is crucial, ensuring that additional tasks don't overshadow core duties.

4. Navigating the Role of Staff+ IC Leaders by Silvia Botros (Estimated Reading Time: 9 mins): Key Learning: The ambiguity of Staff+ IC roles demands a balance of responsibility and boundary-setting to avoid overextension.

   ---

   💡Mental Model of the week:

   • The Napoleon Technique: Strategic Task Postponement (Estimated Reading Time: 5 mins): Discover how postponing certain tasks can enhance focus and problem-solving, based on Napoleon’s technique.

     ---

     Conclusion

     

     This edition brings to light the less visible but equally important facets of leadership in engineering. Your thoughts and experiences are always welcome. Share your insights, and let us know what topics you'd like me to cover next.

Welcome to the second edition of Engineering Leaders Weekly! This week, we are exploring two important topics: the different types of Engineering Managers (EMs) and Staff Engineers, and how to be a good mentor. Let’s jump in!

Understanding EMs and Staff Engineers

1. 5 Engineering Manager Archetypes by Patrick Kua (Estimated Reading Time: 7 mins): Patrick talks about five types of EMs, each with their own strengths and challenges. Knowing where you fit in can help you play to your strengths and work on your weak spots. Having a mix of these archetypes in an organization can foster a well-rounded engineering leadership.

2. Staff Engineer Archetypes by Will Larson (Estimated Reading Time: 6 mins): Similarly, Will explains the different roles of Staff Engineers. Like with EMs, different Staff Engineers bring diverse strengths to the table. A blend of these archetypes can enrich the technical leadership and contribute to a balanced and effective engineering team.

   ---

How to be a Mentor

1. Advice on Technical Mentorship (Estimated Reading Time: 7 mins): If you're looking for practical advice on technical mentorship, John’s piece is a great resource. This article is a guide for those looking to offer technical mentorship, with practical tips on how to effectively support and guide mentees towards achieving their goals.

2. What Sponsorship Looks Like by Lara Hogan (Estimated Reading Time: 10 mins): In this piece, Lara delves into the concept of sponsorship, an essential aspect of mentorship, and how it can make a difference in advancing careers.

3. Supporting Women as Senior Leaders by Lara Hogan (Estimated Reading Time: 10 mins): Lara shares her insights on mentoring and supporting women in senior roles, emphasizing that “women are over-mentored, and under-sponsored.” Her advice is crucial for building a supportive and inclusive workplace.

4. Being the Mentor You Wish You Had by Career Cutler (Estimated Reading Time: 8 mins): This article delves into the essence of being a good mentor and how to foster a positive mentor-mentee relationship.

   ---

Setting Practical Goals

• Engineering Goal Examples: Setting clear and achievable goals is the key to success. Here are some practical goal examples for various folks.

What are your thoughts on the different roles of EMs and Staff Engineers? How are you embracing mentorship within your team?

Stay tuned for more insights in the next edition. Until next week, keep learning and growing!

This week, we delve into the heart of engineering - problem-solving. The lens through which you view and untangle problems can profoundly impact your journey. Here, we've curated four compelling reads to enrich your problem-solving toolkit.

Let's dive in!

1. Completed Staff Work: The Art of Problem-Solving (Estimated Reading Time: 7 mins): Discover the methodical approach of Completed Staff Work (CSW) in solving problems comprehensively, ensuring all facets are addressed before decisive actions are taken.

2. 30 Ways to Think About a Problem by Marcus Fernström (Estimated Reading Time: 8 mins): Marcus unfolds a kaleidoscope of 30 perspectives to refine your approach towards problem-solving. His variety of lenses may spark a new way of tackling your engineering challenges.

3. Don’t Bring Me Problems, Bring Me Solutions by Seth Falcon (Estimated Reading Time: 6 mins): Seth dives into a common managerial mantra and explores why a solutions-only mindset can be limiting. His reflections pave the way for fostering an innovative and open problem-solving environment.

4. Avoiding the Hard Problem Trap from Arjit (Estimated Reading Time: 5 mins): Delve into the temptation of complex problems and how they can sometimes deviate teams from the main goals. This post offers insights on aligning your problem-solving journey with the broader mission.

   ---

   Your feedback is the compass guiding this newsletter. Reach out to me via email or LinkedIn for sharing your thoughts.

   ---

   Share