Operations | Monitoring | ITSM | DevOps | Cloud

Lauren Craigie (Head of PMM at Cortex) is joined by Justin Reock, Head of Developer Relations at Cortex for a conversation about meausuring developer productivity.

In 2023 most engineering organizations have some way of measuring productivity. Metrics like story points and cycle time help us assess team-wide impact, while code coverage and commits tell us more about individual contributions. While we know these numbers don’t tell the whole story, we rarely hear about how to find the missing pieces. Or what to do next when we learn the culprit is poor testing practices versus bad design. What’s the plan for improvement? Where does it live, and who owns it?

In the last 5 years, we’ve watched the world's fastest growing engineering teams ditch development monoliths in favor of service-oriented architectures that speed time to market. And as microservices multiplied—making it harder to track ownership and quality—Internal Developer Portals (IDPs) emerged to help. But while the prospect of a single portal for developer productivity sounds enticing, veteran leaders know the perception of “one more tool” can make org-wide adoption challenging.

Internal developer portals (IDPs) have received a lot of attention lately. Internal Developer Portals serve as the engineering system of record—providing developers with the context and tools they need to ensure services and resources they own align with best practices for deployment readiness, operational maturity, security compliance, and more. But they do more than just act as a system of record for your whole stack. They also help drive alignment, improve MTTR, and can even reduce cloud spend.

Back by popular demand, Ganesh Datta will cover Developer Portals and why users look to Cortex for running efficient engineering teams. Developer portals have become increasingly important to run an efficient engineering team especially as the number of services or engineers scale. Learn more about why companies adopt developer portals, how to maximize their impact, and how they can help your team reduce the organizational complexity that comes with running a service oriented architecture.