
How to Turn Faster Coding into Faster Shipping: Delegation, Verification, DevEx Data
>
Here are 15 deep dive questions you can ask your developers to uncover the causes of friction in code review, along with guidance on how to interpret the results, common patterns engineering teams encounter, and practical first steps for improvement. This will help you pinpoint what’s causing the problem and fix it on your own, or move faster with our DevEx AI tool and expert guidance.
>
Use DevEx survey questions to uncover friction in live debugging. Learn how engineering teams diagnose production issues faster and reduce incident response time.
>
Last year, the dominant story was the “70% problem”: AI helps you get surprisingly far, surprisingly fast—but the final stretch toward production readiness becomes a grind of edge cases, debugging, and diminishing returns.
>
How VPEs Break the “AI Paradox” with Orchestration and DevEx Signals
>
Learn how DevEx survey questions uncover specification clarity issues, reduce rework, and improve delivery using real developer feedback and DORA insights.
>Hosted by Anita Zbieg, PhD, this session will feature industry experts Simon Boudrias (Director of Engineering at Datadog) and Jon Kern (Software Engineer, Agile Manifesto Co-author at Adaptavist). Together, they will share insights on cultivating a developer culture that is not just productive but customer-centred.
>How to Spot the Good and Avoid the Bad in Code Review Signals?
>
Thematic public Slack channels are for fun and bring people together around common interests, hobbies, and lifestyles.
>
This feature helps reduce meeting fatigue and stress by providing attendees with some much-needed downtime between meetings.
>
If you want to communicate, choose primary communication channels the tools where the work is done. This way you’ll improve productivity and reduce communication time
>How to balance time for focused work and meetings in dev teams at scale?
>
Booking page is especially handy for meetings organised with people from outside the company.
>Use public chat channels instead of private, if the subjest is not confidential, or private.
>Let’s take a holistic view of the CI/CD pipeline. It is a delivery mechanism, but its role goes beyond just building code—it also builds developers' daily experiences.
>
Focus on what truly matters: the users’ actual experiences and the value they gain while using your product—even down to endorphin levels. This includes those that drive reward and motivation, like clicking a link and expecting it to load instantly, as well as those that sustain long-term satisfaction. These are the experiences your software can strive to deliver and optimize for.
>