Building effective development teams hinges on prioritizing the developer experience. Poor tooling and inadequate support lead to cumbersome builds and inefficient workflows, creating friction that slows engineers and hinders their ability to deliver value. Join this peer discussion to share and discover practical strategies for boosting developer velocity and satisfaction. > How can we effectively measure the developer experience to pinpoint specific friction points that negatively impact team velocity and satisfaction? > What tools or strategies effectively boost knowledge transfer, reduce cognitive load, and accelerate onboarding? > What are your team's biggest DX pain points with builds, IDE, or CI, and what proven leadership tactics address them? > Where does your team experience the most friction day-to-day (e.g., with builds, IDEs, CI/CD, inefficient workflows)? What practical leadership tactics or tooling improvements have successfully addressed these pain points? > How can engineering leaders effectively quantify the impact of DX improvements on velocity, satisfaction, or overall value delivery to justify necessary investments to stakeholders?

Repetitive tasks, complex command-line actions, and the need to enforce team standards often disrupt the development workflow and force the developer to leave their IDE. Integrating essential tools and documentation directly into the IntelliJ IDE offers a significant productivity boost by minimizing context switching and streamlining common processes.This lightning session demystifies IntelliJ IDE plugin development, demonstrating its accessibility. It will cover how to get started with building practical, simple plugins using patterns and frameworks you already know today such as Compose.