Constant change is all but inevitable on most software engineering teams. According to the Bureau of Labor Statistics, the median tenure for computer and mathematical occupations is just 4.4 years; software engineering teams often see developers rotate out after 2 years or less. Startups rise and fall. Reorganization is common. Attrition is high. How can you keep a team performing when the environment is in constant flux? Kathleen Vignos offers tips, shortcuts, and stories for stabilizing a team and finding a path to productivity amid the chaos as she walks you through engineering-specific real-world examples of how to keep #ShippingIt.
Kathleen Vignos is a full stack engineer turned manager who has led engineering teams at Twitter and Wired. She’s worked at two startups (one of which she founded), traveled the western US for management consulting and professional services, taught business software programming at the university level, won a hackathon, and built dozens of websites. Other experiences include everything from being on call as a COBOL programmer for Y2K to modifying a React app for a hack week project. She holds engineering degrees from UCLA and Michigan.
Comments on this page are now closed.
For exhibition and sponsorship opportunities, email email@example.com
For information on trade opportunities with O'Reilly conferences, email firstname.lastname@example.org
View a complete list of Fluent contacts
©2017, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com
Excellent presentation. Thanks for a peek into how development management can work from the inside point of view.