Dr. Nicole Forsgren is best known for her work measuring the technology process and as the lead investigator on the largest DevOps studies to date. She has been a professor, sysadmin, and performance engineer. Nicole’s work has been published in several peer-reviewed journals. Nicole earned her PhD in Management Information Systems from the University of Arizona, and is a Research Affiliate at Clemson University and Florida International University.
Heather Rivers is the CTO of Mode, an analytics platform allowing over 500 organizations to make better decisions with their data. Before that, she spent a decade building software at a variety of other companies, from early stage startups to Microsoft.
Cynthia Maxwell has led product teams that helped make it possible to use your phone for making video calls, reading books, communicating on Slack, or browsing Pinterest. With a path that has taken her from academic work in computer science through VR at NASA Ames Research Center to Apple, Pinterest, Yahoo and Slack, Cynthia has been a leader in the software industry for 20 years with a front-row seat to several major platform shifts.
Bryan Helmkamp is the founder and CEO of Code Climate, where he helps software development teams improve code quality. Over the past six years, Code Climate has helped thousands of organizations improve their code review workflows and ship better code in less time. Prior to Code Climate, Bryan was CTO at Efficiency 2.0, a company focused on using science to help people lower their energy use, and also an engineer at Gilt Groupe. He has given talks on software engineering principles and practices around the world. Bryan co-authored the book “Service Oriented Design with Ruby” and also “The RSpec Book”.
Rodrigo Miguel has worked in the software development industry for about eighteen years. He is passionate about people and teams, and his mission is to continuously improve the software development process by finding bottlenecks, eliminating waste, reducing time to market, and helping people to improve their skills. Currently, he is a Software Engineering Manager at Resultados Digitais, which is a fast-growing tech company from Brazil. Resultados Digitais has a product named RD Station Marketing, a marketing automation platform with 15,000 customers from more than twenty countries around the world.
Sumeet Jain is the Development Director at Unabridged Software, in Omaha, Nebraska. During his 13-year career in web development, Sumeet gained experience at various companies in Silicon Valley from corporations and agencies to small startups. While he has now landed in the familiar arena of engineering management, it's his atypical foray into education running a regional coding school in Nebraska that propelled Sumeet's understanding of building and training teams. Sumeet loves developing for the web, but his latest passion is building teams that grow gracefully and creating software development processes that make everyone's life a little easier.
Ale is a passionate Software Engineer with over 7 years of experience focused on creating resilient and scalable systems. Currently, Ale works at Code Climate, where she spends her time thinking about system architecture, communication and organization skills, and how to build a healthy and inclusive team. Also, she is one of the founders of Latinas in Tech NYC.
As the leader of the internationalization engineering team at Asana, I had the opportunity to work with our engineering, product, design, sales, customer support, marketing, and legal teams to ensure that we launched our multi-language support on time. Later, I was instrumental in coordinating our many engineering efforts to ship our GDPR compliance on-time. My experience as an API engineer at Stripe and a Tech Lead at HubSpot also gives me another perspective of how cross-team collaboration works at different companies.
I think it’s really interesting that a conversation can often be 5 people but rarely be 6. I’m fascinated by minor technical / product decisions that have ramifications that spiral outwards for years. I’m frustrated by the myths that Silicon Valley tells itself about itself. I’m skeptical about startups that claim that they’re revolutionizing the world, but I still aspire to it. I’ve been an eng manager at Asana for almost three years, and currently lead the ~20 engineers who work on growth and adoption.
As a manager, time is one of your most precious resources, and it can be a challenge to allocate it effectively and efficiently. In my presentation, I will be focusing on simple tools to help you focus and plan your day. We will start by breaking down the major job functions of a manager and then explore detailed examples of strategies to resolve competing priorities. You will learn resources that work for me personally as a manager. I will also discuss the inevitable question, “Am I spending too much time on this one thing”. We will also go a bit deeper to discuss tools for supporting yourself as a leader. By the end of our discussion, I hope that you will have the tools to be able to quickly judge where your attention is most needed at any given time and how to find strength and resilience as a leader.
Does the size of the pull request matter? If yes, what should be its ideal size? In this talk, I will explain why it is important to be concerned with the size of the pull requests and what should be taken into account to understand what is the ideal size. We will look at the impact on the quality and speed of development that the size of the pull requests can cause, understand the costs associated with working with large or small PRs, and show the relationship with the queueing theory.
The barrier to entry in software has been trending downward since before the dawn of Unix time. Accordingly, the sustained pace of software delivery has become a powerful predictor of success. When problems arise, this urgency can prevent us from delving deeply into the root causes of the problems that all too commonly plague teams of software developers: bugs, downtime, missed deadlines, broken builds. This talk will explore the question: where can we look to understand the source of these problems more deeply, without slowing down to do it?
As part of a small engineering team in a startup, you often find yourself drowning in ambitious goals, large problems, and constant changes. How can small teams achieve high velocity in a fast-paced environment? During this presentation, we will share the process we use internally to tackle these challenges at Code Climate. You will walk away from this presentation with practical suggestions for your team on how to approach large projects.
Getting things done requires teamwork. As engineering leaders, we like to focus on our immediate team of reports, rather than the wider team of the rest of the organization. We like to leave our senior leadership to be the connective tissue between teams and departments.
The best engineering leaders know that true impact requires teamwork that reaches across organizational boundaries. While working on internationalization at Asana, I learned some powerful communication habits and completely changed the way that I thought about cross-team collaboration. I’ll be showing you some practical strategies to try the next time you want to have a big impact with your organization.
People change jobs very frequently in tech, causing churn and lost leadership. One reason is that engineers get bored, or feel stuck in their current role. How do you help your reports change jobs without changing companies? We’ll go over some concrete actions, including:
Everyone is frustrated about hiring, onboarding, and retention. This is what happens when we value something, like mentorship, without knowing how to achieve it. Worse is that much of the advice out there is not actually tactical... Instead it’s just more reasons why we should value mentorship. This talk is not about valuing mentorship. No one needs to be convinced of that anymore. The more interesting question is assuming you already value mentorship, what tactics can you immediately add to your internal playbook? Companies that can grow talent from within have a huge advantage. But without realistic and actionable tactics, that advantage will always be out of reach. This talk will change how teams approach training by handing them several usable strategies, and by giving them a framework to create their own playbook.
How do you become a high performing technology organization? Over the past four years, the State of DevOps Report has shown how high-performing IT teams decisively outperform low-performing peers. The report has also investigated the effects of burnout, culture and employee engagement on organizational performance. Nicole Forsgren shares insights into the key leadership, technical, architectural, and product capabilities that drive these outcomes. She offers highlights uncovered over the last four years from the 23,000+ responses.