Kat Cosgrove is a Developer Advocate, a CNCF Ambassador, and an actual cyborg. Her professional background has run the gamut from bartender, to video store clerk, to teacher, to software engineer. She credits this wide-ranging experience for her success as a speaker, developer, and advocate. You can usually find her speaking about DevOps or cloud native technologies, particularly 101-level content, in pursuit of her goal of increasing accessibility for these tools.
When she's not building demos or at a conference, she spends her time playing video games, watching horror movies, and reading science fiction. She lives in Seattle with her cat, Espresso, who is the real brains behind the operation. Espresso may be ghostwriting her tweets.
There are more computer science graduates than ever, and the number keeps rising. Include coding bootcamp graduates, and the number of junior engineers out there is staggering. Sounds great, right? More engineers means larger communities and more help for our projects, and the whole world benefits because we’re solving harder problems faster. That's what DevOps is about, yeah?
It’s not quite that simple. Tech is advancing quickly, becoming more and more specialized, with layers upon layers of abstraction and tooling. We frequently assume that the people reading our documentation and using our tools already have context and peripheral knowledge specific to our corner of tech, and we forget about all of those junior engineers with fresh ideas who are hungry to learn, but don’t understand our jargon. We don't mean to do it, but we're gatekeeping them, and it's slowing our progress. In order to really accelerate DevOps adoption, WE need a cultural change, too.
When you’re new to an industry, you encounter a lot of new concepts. This is especially true with DevOps, a fairly young corner of tech where things move very quickly, by design. Some of the concepts we consider central to DevOps are actually pretty old, though -- predating the birth of DevOps by a decade or more. Without this context for how things evolved, and for the specific ways in which software development was more difficult without the methodologies and toolsets we have today, grasping the "why" for modern abstractions can be difficult. Without understanding the "why," learning to use a new tool well isn't as easy as it could be.
In this talk, you'll learn about the history of CI/CD: the birth of the concepts that led to what we have today, the slow evolution of tools along the way, and how this has fundamentally changed what software development looks like over the last thirty years.