You must be a LeadDev Berlin 2024 ticket holder to proceed
Ticket holders must sign in to LeadDev.com with exactly the same email address as stated on your LeadDev Berlin 2024 ticket.
Do you have a LeadDev.com account matching the email address on your ticket?
My email is not recognised or, having signed in, it says I do not have access to the content
Double check your ticket to make sure that you are trying to access with the correct email address (see below for where to find your ticket).
If you're sure that the ticket is correct, get in touch via Slack and we'll investigate for you
The verification email does not arrive
Check your spam and/or junk folders for the email. We know that some corporate email firewalls block our emails, and in this case you'll need to get in touch (see below) for us to move your ticket to an alternative email address.
The verification email link does not work
The links are time limited, so make sure you've tried in the last few minutes. If not, some corporate email firewalls have occasionally corrupted the verification links, and in this case you'll need to get in touch (see below) for us to move your ticket to an alternative email address.
Where can I find my ticket?
Your ticket will have been emailed to you from support@tito.io (Tito is our ticketing provider). If you don't have an email from Tito with your ticket, check with the person who made the booking originally. Otherwise, get in touch and we'll be able to help.
Getting help
The quickest way to get support is via our #help-desk channel on Slack (not a member of LeadDev Slack? join here.)
You can also email hello@leaddev.com although response times will be slower.
More like this
Embark on a journey of innovation and empowerment as we explore the transformative impact of scaling on-call across multiple teams.
In this talk, I’ll dive deep into our story, the challenges, solutions, and the iterative process of implementing a unique on-call rotation when traditional SRE support was unavailable.
Discover how this approach not only reduced costs and complexity but also empowered developers to take ownership of their services, fostering a culture of collaboration, knowledge sharing, and continuous feedback.
Join me to learn how this new setup improved service quality, and documentation, and brought teams together as a cohesive unit.
Key takeaways:
- Strategies for effectively scaling on-call across multiple teams in the absence of traditional SRE support.
- Insights into reducing costs, complexity and empowering developers to take ownership of their services through innovative on-call rotations.
- Inspiration to implement similar approaches in your organization, driving service quality, documentation, and team cohesion.
