Skip to content

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.

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

Agile vs. Waterfall: Finding the Right Mix in Software Engineering with Dustin Goodman, Engineering Manager at This Dot Labs cover image

Agile vs. Waterfall: Finding the Right Mix in Software Engineering with Dustin Goodman, Engineering Manager at This Dot Labs

In this episode of the Engineering Leadership series, Tracy Lee and Dustin Goodman shed light on the advantages of combining different project management processes to create a more efficient and effective workflow. Dustin, an engineering manager who works at the development consultancy This Dot Labs, shared his insights on how he recently helps companies optimize their engineering processes. To illustrate, Dustin shared an example of a project he worked on. The company was aiming to deliver a feature set in three to four weeks. By implementing a combination of waterfall and agile methodologies, they were able to break down the project into smaller, manageable tasks and deliver results incrementally. This not only improved efficiency but also allowed for quicker feedback and iteration. One of the key takeaways from the discussion was the importance of understanding the highest value proposition and how it aligns with the organization's key performance indicators (KPIs) or objectives and key results (OKRs). By identifying the most valuable aspects of a project, teams can prioritize their efforts and ensure that they are delivering the most impactful results. Planning and flexibility were also highlighted as crucial elements in creating an effective workflow. While upfront planning is necessary to set clear goals and expectations, it is equally important to remain flexible and adapt to changing circumstances. This balance between planning and flexibility allows teams to respond to new information and make necessary adjustments without derailing the entire project. Tracy and Dustin also mentioned the example of 37 Signals, a company that follows a six-week timeline for each project from inception to delivery. This approach emphasizes the importance of setting realistic deadlines and maintaining a sense of urgency without sacrificing quality. Combining different project management processes, such as waterfall and agile, can create a more efficient and effective workflow. It is important to understand the highest value proposition and how it relates to the organization's KPIs or OKRs. Planning and flexibility are key, and it is important to be able to plan for the long-term, but also be able to pivot quickly when needed....

Being a CTO at Any Level: A Discussion with Kathy Keating, Co-Founder of CTO Levels cover image

Being a CTO at Any Level: A Discussion with Kathy Keating, Co-Founder of CTO Levels

In this episode of the engineering leadership series, Kathy Keating, co-founder of CTO Levels and CTO Advisor, shares her insights on the role of a CTO and the challenges they face. She begins by discussing her own journey as a technologist and her experience in technology leadership roles, including founding companies and having a recent exit. According to Kathy, the primary responsibility of a CTO is to deliver the technology that aligns with the company's business needs. However, she highlights a concerning statistic that 50% of CTOs have a tenure of less than two years, often due to a lack of understanding and mismatched expectations. She emphasizes the importance of building trust quickly in order to succeed in this role. One of the main challenges CTOs face is transitioning from being a technologist to a leader. Kathy stresses the significance of developing effective communication habits to bridge this gap. She suggests that CTOs create a playbook of best practices to enhance their communication skills and join communities of other CTOs to learn from their experiences. Matching the right CTO to the stage of a company is another crucial aspect discussed in the episode. Kathy explains that different stages of a company require different types of CTOs, and it is essential to find the right fit. To navigate these challenges, Kathy advises CTOs to build a support system of advisors and coaches who can provide guidance and help them overcome obstacles. Additionally, she encourages CTOs to be aware of their own preferences and strengths, as self-awareness can greatly contribute to their success. In conclusion, this podcast episode sheds light on the technical aspects of being a CTO and the challenges they face. Kathy Keating's insights provide valuable guidance for CTOs to build trust, develop effective communication habits, match their skills to the company's stage, and create a support system for their professional growth. By understanding these key technical aspects, CTOs can enhance their leadership skills and contribute to the success of their organizations....

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....