You must be a ticket holder to proceed
Ticket holders must sign in to LeadDev.com with exactly the same email address as stated on your 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
Some bugs haunt the team for weeks. Recurring, hard-to-track, embarrassing. They ruin the road maps, kill morale and undermine stakeholders’ trust. If you ever seen them, you know the nightmare.
Don’t despair – I’ve found a way to deal with them efficiently. A mix of methods and habits used by scientists is the way out of debugging horror. It’s a loop of observation, hypotheses and experiments, enhanced with practices used by scholars. It makes debugging more predictable, less frustrating and much faster. I’ll share how they helped me in three case studies: fixing a non-deterministic test, stabilising CI infrastructure and resolving a recurring production downtime.
This talk will enhance your programming toolbox for the hardest bugs. Not only this – but you’ll see how to scale effective debugging to the entire team. Last but not least – you’ll leave with a set of habits to share with your fellow engineers to help them step up their debugging game.
