The industry is still asking more questions than its answering around #DevEx, Platform Engineering, and even (still!) #DevOps! Hear from Cortex's very own Head of Developer Relations, Justin Reock, get together and talk with other interested minds helps move us more collectively to answers and solutions that can improve the flow, productivity, and ultimately joy of our workforce! Full description.

98% of engineering leaders reported at least one major consequence of failing to meet production readiness standards. To better understand how teams are addressing new challenges in production readiness, Cortex recently conducted a survey of engineering leaders at companies with more than 500 employees in North America, Europe, and AsiaPac. The survey included questions pertaining to production readiness standards, tools, struggles, and desired future state.

DevOps solutions have evolved quickly over the last few years. Software catalogs have bloomed beyond service registries and runbooks into comprehensive, centralized engineering sources of truth. With ever-expanding developer tool sets, can teams achieve the flexibility needed to address this fragmentation while continuing to tailor software catalog entries to their unique domains and contexts?

While we know software projects are never truly “done,” developers will, nevertheless, often face a long list of tasks needed to achieve a certain level of “doneness.” But to what end? And when do they end? When is done—done enough? In this fireside chat-style webinar, Justin Reock - Head of DevRel for Cortex - alongside Alina Anderson - Principal Technical Program Manager at Outreach - will explore an evolved approach to determining production readiness.

Hydrate your catalogs with ownership info in under 10 minutes.

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?