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.
In this talk, media server engineer Josh McNamee discusses the challenges in shipping Disguise’s ‘Single Large Canvas’, the software feature that lets U2 put images on the inside of the Las Vegas Sphere.
Across disciplines and time zones, the team worked through a series of complex challenges to deliver a pipeline to let 23 machines fill a 16k video wall. Live events work to very short deadlines, where a whole project can come together in a matter of days before the band walks on stage. In this environment, software issues can and do emerge at the eleventh hour and have to be carefully triaged, tracked and resolved with confidence.
As the scope of customer requirements shifted and came into focus, the project expanded from a team with a single engineer and grew rapidly over three months. Members were split across two continents, stamping out bugs in overlapping shifts and shuttling information back and forth between in-house testing and on-site testing.
Discussing both the managerial and technical challenges, this talk will go through what worked, what didn’t, and what lessons were learned for the next show – which was only six months later!
