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.
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.
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!
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.
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.
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.
Aish Raj Dahal touches upon this slightly less talked about aspect of the job as a technical IC leader, which is creating peer relationships and working with other Staff engineers in shaping an organization’s technical roadmap.
James Ford reflects on his two year journey as a Staff Engineer and how a mix of documentation and working groups has been a surprisingly effective strategy for influencing the opinions of the individual engineers as well as the non-technical stakeholders.