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
No carrots, no sticks. How can I make my colleagues do things?
The role of a Staff Engineer often involves work across the org chart, reaching out to unfamiliar teams and colleagues with competing incentives and varying levels of enthusiasm for our unsolicited bright ideas. With no direct reports to instruct, no cash to flash, and no authority to wield, overcoming the inertia of large-scale, cross-cutting projects can seem daunting. Technical Diplomacy is the long game of building relationships, understanding, and a shared vision to make collective progress.
We’ll follow a multi-team project where organisational dynamics had shaped some architectural decisions and inter-team friction was clouding our judgement. We’ll look at how empathy, inclusive language, and collaborative exercises helped to break the impasse and bring a feature from hunch to implementation. We’ll also consider international diplomacy to see the surprising parallels between API design and negotiating with terrorists.
You should leave this talk curious and keen to apply technical diplomacy to your role. You’ll have some ideas for where to start, and what you can do together with your colleagues to build a better understanding. You’ll be able to spot obstacles and will have some tricks up your sleeve for getting around them. And you’ll have no excuse for repeating my silly mistakes. Ultimately, you’ll be ready to embrace your colleagues — even the difficult ones — in the pursuit of shared success.
Key takeaways:
- Preparation for the unknown: Consider extremes, and present examples instead of options
- Activities to build shared understanding
- Little and big things to try when you’re faced with resistance
- Radical empathy: Challenge cynicism, listen, persist, take no nonsense
