Our Blog
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
•
April 1, 2024
Missing dimensions in development ops & productivity metrics
Engineering Managers have a variety of metrics they can draw from to assist in understanding their teams' efficiency & operational performance. What’s missing is a precise measurement of risk (i.e. complexity) and Resilience (i.e. mitigation effort).
Read More
•
March 14, 2024
Inside the prediction of a bug that led to a CVE in Redis
Our predictive model highlighted the risks leading to a CVE in Redis, showing the importance of objective risk assessment over traditional methods. This blog delves into the misconceptions about small pull requests and conventional mitigation's limitations
Read More
•
February 16, 2024
Go deeper on Cycle Time with Risk & Resilience
Engineers experience cycle time through risk and complexity trade-offs. Shepherdly helps teams measure this and codify their risk tolerance.
Read More
•
August 7, 2023
Benchmarking Risk & Quality KPIs in Popular Open Source Projects
Analyzing six popular open-source repositories, Shepherdly examined how various established and novel quality KPIs are reflected in some of the most extensively used software tools.
Read More
•
July 12, 2023
Why it’s time for devs to focus on AI bug detection
From ChatGPT to GitHub Copilot, generative AI is here, and with it has come scores of new technology that’s making it easier than ever for developers to complete coding tasks faster, innovate, and create better software.
Read More
•
June 23, 2023
AutoReviewer: Bug History-Guided Code Review
In addition to predicting the likelihood of a PR causing a bug, Shepherdly adds even more context to the bug hotspots in your code when modified.
Read More
•
May 10, 2023
Why Software Engineers Need Better Risk Assessment Tools for Pull Requests
As a software engineer, you may have shipped something that you and the reviewers knew was risky, but it was too expensive to investigate the issue further. You may have added remediation steps, but time pressure may have prevented you from doing so.
Read More
•
April 1, 2024
Missing dimensions in development ops & productivity metrics
Engineering Managers have a variety of metrics they can draw from to assist in understanding their teams' efficiency & operational performance. What’s missing is a precise measurement of risk (i.e. complexity) and Resilience (i.e. mitigation effort).
Read More
•
March 14, 2024
Inside the prediction of a bug that led to a CVE in Redis
Our predictive model highlighted the risks leading to a CVE in Redis, showing the importance of objective risk assessment over traditional methods. This blog delves into the misconceptions about small pull requests and conventional mitigation's limitations
Read More
•
February 16, 2024
Go deeper on Cycle Time with Risk & Resilience
Engineers experience cycle time through risk and complexity trade-offs. Shepherdly helps teams measure this and codify their risk tolerance.
Read More
•
August 7, 2023
Benchmarking Risk & Quality KPIs in Popular Open Source Projects
Analyzing six popular open-source repositories, Shepherdly examined how various established and novel quality KPIs are reflected in some of the most extensively used software tools.
Read More
•
July 12, 2023
Why it’s time for devs to focus on AI bug detection
From ChatGPT to GitHub Copilot, generative AI is here, and with it has come scores of new technology that’s making it easier than ever for developers to complete coding tasks faster, innovate, and create better software.
Read More
•
June 23, 2023
AutoReviewer: Bug History-Guided Code Review
In addition to predicting the likelihood of a PR causing a bug, Shepherdly adds even more context to the bug hotspots in your code when modified.
Read More
•
May 10, 2023
Why Software Engineers Need Better Risk Assessment Tools for Pull Requests
As a software engineer, you may have shipped something that you and the reviewers knew was risky, but it was too expensive to investigate the issue further. You may have added remediation steps, but time pressure may have prevented you from doing so.
Read More