Speaking Rubber Duck: How to Be Your Own Developer Advocate

The final test is written, the code is merged into main, and the Jira ticket is closed but the work isn’t over yet. Now it’s up to other teams in your organization to communicate that work to stakeholders — whether that's a paying customer or a team lead whose role will be directly affected by your changes.From explaining why a complex feature took that long to complete, to enabling your training department to deliver training on the latest release you've been working on, everybody benefits when your work is clear and easy to understand.In this talk, you'll find out how to become your own developer advocate. We'll share practical strategies to communicate your work more clearly, collaborate better with non-dev teams, and build visibility for your contributions