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
It is well understood that developing solutions to complex problems is not an industrial process.
It is full of uncertainties, research, ongoing problems and stoppers, but since these solutions always have a supporting business case, we have to be ready to deal with plans and schedules for getting things into production.
In this regard, one of the most difficult tribulations in routine work in the tech industry is when somebody asks for an estimate. If you want a seasoned senior engineer to sweat, ask them for an estimation over a user story: “When will this be ready?”. I have always felt that the underlying problem is that expectations and roles over this process have never been correctly understood.
This way, we usually think about estimations in terms of the cost and effort needed for developing a feature, but in reality, the conversation is all about when something will be ready.
What if we could change our mental model about estimations? What if there is a model that removes toil from the process while increasing trust and commitment?
In this talk, I propose a method of switching estimations from cost and effort to a probability map for time of delivery, making conversations about estimates easier with engineers and useful for stakeholders in order to have a better answer to … “When will this be ready?”
