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.
Let’s talk about migration, especially the less spotlighted part: the process of dismantling the legacy system. How do you go about it? How did others approach it?
In this talk, I’ll share the strategies used to disassemble our legacy data pipelines responsible for managing merchant eligibility on the Shop apps. Join me on a journey through our successes, challenges, and invaluable learnings in the meticulous orchestration of terminating our legacy data pipelines.
- Gain insights into the rationale behind opting for the strangler pattern over the quick-and-easy rip-and-replace strategy, and understand the trade-offs we accepted with this intentional decision.
- Explore the implementation of the factory method pattern to seamlessly integrate the numerous new data pipelines we built, unveiling the practical advantages it brought to the process of phasing out the legacy pipelines.
- Learn the art of keeping track of communications with numerous teams and the strategies employed to ensure seamless collaboration.
- Dive into the intricacies of stakeholder communication, understanding the different needs of various areas.
