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 tech, the conventional approach to building systems often assumes planet-scale requirements from the outset, often resulting in architectures that might scale up smoothly but can often burden organisations with unnecessary complexity and costs from the get-go regardless of whether the anticipated user scale materialises or not.
In this talk, Viktor challenges this approach by advocating for adaptability and a return to basics in system design. Drawing from his experiences, he explores the pitfalls of over-engineering and the importance of simplicity and evolvability in scalable architectures. Through concrete examples, including challenges faced at Personio, Viktor will discuss the need to prioritise correctness, ease of reasoning, and understanding of trade-offs when architecting systems for sustainable growth.
Takeaways:
- Prioritising for correctness and simplicity and how to avoid unnecessary complexity that hinders scalability and resource efficiency.
- Understanding how inherent trade-offs and their implications can support the creation of scalable and informed architectural decisions.
- How to optimise systems not just for technology but also for real-world understanding, enabling smoother onboarding of new team members and scalable growth.
