-
The dark side of standardization
Samantha Schaevitz wants you to leave this talk better equipped to decide whether embarking on a standardization project is right for your stack or organization, and how to do it in a way that avoids common pitfalls along the way.
-
Maximizing your impact when context-switching
Maude Lemaire spent the last few years trialing a few different ways to sustainably maximize this time by balancing productivity with a bit of mindfulness. Come learn from her (many) mistakes, and hopefully we can all feel a bit less like a Dalí painting.
-
Why onboarding to a company’s legacy codebase sucks, and how to make it work for your team
Shanea Leven discusses the history and context of the problems that plague codebase onboarding. And with problems come solutions such as tips and tools that make it easier for engineers to onboard a legacy codebase.
-
Engineering transparency
In this talk, I explain why it’s valuable to show our work as Staff engineers. I offer concrete ways to behave transparently and give examples of how each has helped me and my colleagues.
-
Maps to medicines: One map to an atlas
Shweta Bhandare discusses how Recursion scientists perform CRISPR-Cas9 mediated knockout to understand the activity level of every gene in a specific disease model, which allows new discoveries to be made. These maps are specific to a cell-type.
-
Defining a technical vision
Eamon Scullion discusses the role of a technical vision in creating a roadmap for your organisation's technology evolution. We will cover how to assess your current technology architecture, defining your target state and identify next best steps for getting closer to your goal.
-
The dark side of lessons learned
Dianing Yudono explains how you can boost the efficiency and effectiveness of your software development processes by unlocking the power of lessons learned and making them accessible to everyone. Let's elevate our collective wisdom and drive success together!
-
Defining expectations of Staff Engineers
This presentation is mainly targeted for Staff Engineers who work on defining their own roles and responsibilities. Writing a Staff Engineer Guide, and agreeing on the expectations between the engineering and the management, is a great way to learn about your organization.
-
Scaling your influence when you can only be in one place at once
Michael Tweed will cover a case study of the problem "how do we ensure all our teams are meeting code quality standards", looking at approaches that are likely to (and have!) failed, vs. those which are much more likely to lead to results and long-lasting buy-in.
-
Setting goals as a staff+ engineer
Sabrina Leandro shares how to define your development journey as a staff+ engineer, figuring out what you should be working on, how to set your goals, and how to you define your backlog of work. You’ll also learn how to track your progress so you can keep growing as an engineering leader in the individual contributor track.