Why doing difficult things is good for you and good for your team - Katie Bickford

[EuroPython 2026 - S2 on 2026-07-15] 🎤 *Why doing difficult things is good for you and good for your team by Katie Bickford* 🔗 https://ep2026.europython.eu/session/why-doing-difficult-things-is-good-for-you-and-good-for-your-team 📝 Abstract: This talk shares my experience in my first ever role as a junior engineer after switching careers. I picked up a ticket involving tools and concepts I’d never used before (OpenTelemetry and Honeycomb), hoping to spend a day learning a bit about how we implement observability and monitoring of our Django app. Spoiler alert: it took three weeks of learning, debugging and asking for help to complete this work. I learned some valuable lessons along the way, not just technical stuff, but about how to problem-solve, collaborate effectively, and keep going in the face of *seemingly unending* challenges. Through this talk, I want junior engineers in the audience to know: - You can do difficult things, even if you think you lack the experience or knowledge required. If you’re willing to learn, and have a supportive team around you, you have everything you need. - Doing difficult things is daunting, but also incredibly rewarding. You often learn 10x more than you expected, and when you finally merge your work into main, it feels like winning the lottery. - Taking on hard things benefits the whole team—others might learn something new, or strengthen their own understanding by helping you out. - There’s a lot you can do to support yourself: reach out early, reach out often, and learn how to communicate problems clearly. - The value of your work cannot be measured by lines of code, it’s so much greater than that. This talk also offers a reminder to seniors, and leaders or managers, about how tough it can be to be new. Juniors don’t just lack experience, we don't know what we don't know and it's *really* easy (for others and ourselves!) to underestimate this. When things break or go wrong, we might not understand where or why, and even if we find a bug or an error, knowing how to fix it is another challenge altogether. I’ll share how my team’s support made all the difference, and offer some practical ideas for how others can support their junior colleagues, too. This isn’t a super technical talk. It’s more about the human experience of being a beginner, the value of persistence, why asking for help is a great thing to do, and the power of supportive teams; there's hopefully something useful and/or interesting in this for everyone. --- This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License: https://creativecommons.org/licenses/by-nc-sa/4.0/