Skip to content

How to Interpret Software Developer Performance Metrics with Jimmy Jacobson, CTO of Codingscape

In this episode of the Engineering Leadership series, Tracy Lee sits down with Jimmy Jacobson, the CTO of Codingscape, to discuss the current state of engineering teams and their accountability in today's economy. As the conversation unfolds, Jimmy sheds light on the challenges faced by engineering teams in measuring the impact of changes made within organizations during the economic downturn. He shares that companies are embracing more risky bets and investing in research and development to create new job opportunities and drive growth.

One of the key topics discussed is the measurement of developer productivity. Jimmy introduces frameworks that can be used to assess and track productivity: The Dora metrics focus on key performance indicators such as cycle time, deployment frequency, mean time to restore service, and change failure rate. These metrics provide valuable insights into the efficiency and effectiveness of engineering teams.

On the other hand, the SPACE framework takes a more holistic approach by combining output and stability with team satisfaction and well-being, performance outcomes, activities, communication and collaboration, and efficiency and flow. This comprehensive framework provides a more nuanced understanding of the overall health and productivity of engineering teams.

DX is another framework used by many SaaS platforms out there like Jellyfish and Code Climate for dashboards that can visualize and track teams. These tools provide real-time data and analytics, enabling teams to make data-driven decisions and identify areas for improvement.

In addition to these frameworks and tools, Jimmy introduces McKinsey's framework (or “McCringey” as Jimmy puts it), which emphasizes the ratio of time spent in the inner loop to the outer loop for developers. The inner loop refers to the time spent on core development tasks, while the outer loop encompasses activities such as meetings, planning, and coordination. According to Jimmy, the inner loop is where engineers can have the most impact and should therefore be prioritized. Tools like Jellyfish can be used to collect stand-up data and generate a General Purpose Technology (GPT) for engineering, further enhancing productivity and efficiency.

This Dot Labs is a development consultancy that is trusted by top industry companies, including Stripe, Xero, Wikimedia, Docusign, and Twilio. This Dot takes a hands-on approach by providing tailored development strategies to help you approach your most pressing challenges with clarity and confidence. Whether it's bridging the gap between business and technology or modernizing legacy systems, you’ll find a breadth of experience and knowledge you need. Check out how This Dot Labs can empower your tech journey.

You might also like

Embracing Risk and Doing Your Part in Open Source: Lesson from Platformatic CTO Matteo Collina cover image

Embracing Risk and Doing Your Part in Open Source: Lesson from Platformatic CTO Matteo Collina

In this episode of the engineering leadership series, Rob Ocel interviews Matteo Collina, the co-founder and CTO of Platformatic, a backend development platform that enables users to build APIs using open source tools. Matteo talks about how so many leaders struggle with the concept of risk, leading into a conversation about one of Platformatic's key features: a breaking change detector. This tool leverages data from the user's open telemetry production system to identify potential changes that could disrupt their microservice system. Unlike traditional approaches that rely on fixed sets of information, the breaking change detector uses real data to provide a more accurate and reliable assessment of potential risks. By analyzing actual production data, it offers a powerful way to eliminate the risk of modeling reality inaccurately. Matteo emphasizes the importance of understanding and prioritizing risks for engineering leaders. He believes that leaders must have a deep understanding of the potential risks involved in their projects and be able to make informed decisions based on that understanding. By effectively managing risks, leaders can ensure the success and stability of their engineering initiatives. Furthermore, Matteo shares insights into his team's approach to staying on the cutting edge of technology. He explains that at Platformatic, they are often at the forefront of the Node.js platform, actively experimenting with and testing its experimental features. This proactive approach allows them to identify and address bugs before they become significant issues. By continuously pushing the boundaries and exploring new features, they can provide their users with the most up-to-date and reliable tools. In addition to discussing technical aspects, Matteo also emphasizes the importance of contributing to open source projects. He encourages companies to measure and recognize contributions to open source, as it can lead to a more vibrant and collaborative community. By incentivizing engineers to contribute to open source projects, companies can foster a culture of giving back and create a positive impact on the broader engineering community. Overall, this episode provides valuable insights into the work of Platformatic and Matteo Collina's perspective on engineering leadership. The breaking change detector technology offers a practical solution for detecting potential disruptions in microservice systems, based on real data rather than fixed sets of information. Matteo's emphasis on understanding and prioritizing risks highlights the importance of effective leadership in engineering. Additionally, his team's commitment to staying on the cutting edge of technology showcases their dedication to providing the best tools for their users. Finally, Matteo's call to measure and incentivize contributions to open source projects serves as a reminder of the benefits of collaboration and community involvement in the engineering field....

Navigating Engineering Challenges in the Embedded Space: Insights from Heather Giovanni cover image

Navigating Engineering Challenges in the Embedded Space: Insights from Heather Giovanni

In a recent episode of the Engineering Leadership series, Rob Ocel chats with Heather Giovanni, the VP of Engineering Data Infrastructure at Hewlett Packard Enterprise. They cover the engineering challenges faced in the embedded space, the importance of striking a balance between optimization and customer expectations, scaling up operations, and motivating engineers. Heather Giovanni sheds light on the unique engineering challenges in the embedded space, where optimizing software is crucial while ensuring usability for end-users and maintainability for developers. This delicate balance requires engineers to consider factors like power consumption, size constraints, and performance, all while delivering a seamless user experience. Heather shares valuable insights into scaling up operations in engineering. She emphasizes the need for a strong foundation and a well-defined process to ensure smooth growth. By leveraging automation, standardization, and collaboration, companies can effectively scale their operations while maintaining quality and efficiency. The discussion delves into the topic of motivating engineers to optimize their work. Heather speaks to the significance of fostering a culture that encourages innovation, continuous learning, and collaboration. By providing engineers with challenging projects, recognition, and opportunities for growth, companies can inspire their teams to push boundaries and deliver exceptional results. Heather shares her personal experiences maturing businesses from small to larger ones. She emphasizes the importance of adapting to new processes, embracing change, and leveraging the strengths of a larger organization. This transition requires effective communication, collaboration, and a willingness to learn from others. From striking a balance between optimization and customer expectations to scaling up operations and motivating engineers, the discussion revolves around the engineering challenges encountered in the embedded space and the delicate balance between optimization and customer expectations....

Software Team Leadership: Risk Taking & Decision Making with David Cramer, Co-Founder & CTO at Sentry cover image

Software Team Leadership: Risk Taking & Decision Making with David Cramer, Co-Founder & CTO at Sentry

In this episode of the engineering leadership series, Rob Ocel interviews David Cramer, co-founder and CTO of Sentry, delving into the importance of decision-making, risk-taking, and the challenges faced in the software engineering industry. David emphasizes the significance of having conviction and being willing to make decisions, even if they turn out to be wrong. He shares his experience of attending a CEO event, where he discovered that decision-making and conflict resolution are struggles even for successful individuals. David highlights the importance of making decisions quickly and accepting the associated risks, rather than attempting to pursue multiple options simultaneously. He believes that being decisive is crucial in the fast-paced software engineering industry. This approach allows for faster progress and adaptation, even if it means occasionally making mistakes along the way. The success of Sentry is attributed to a combination of factors, including market opportunity and the team's principles and conviction. David acknowledges that bold ideas often carry a higher risk of failure, but if they do succeed, the outcome can be incredibly significant. This mindset has contributed to Sentry’s achievements in the industry. The interview also touches on the challenges of developing and defending opinions in the software engineering field. David acknowledges that it can be difficult to navigate differing viewpoints and conflicting ideas. However, he emphasizes the importance of standing by one's convictions and being open to constructive criticism and feedback. Throughout the conversation, David emphasizes the need for engineering leaders to be decisive and take calculated risks. He encourages leaders to trust their instincts and make decisions promptly, even if they are uncertain about the outcome. This approach fosters a culture of innovation and progress within engineering teams. The episode provides valuable insights into the decision-making process and the challenges faced by engineering leaders. It highlights the importance of conviction, risk-taking, and the ability to make decisions quickly in the software engineering industry. David's experiences and perspectives offer valuable lessons for aspiring engineering leaders looking to navigate the complexities of the field....