When building reliable services unexpected user behavior can prove deadly. Yet few engineering teams make use of talent from their product and design orgs if they are working on something internal. This talk will demonstrate how a product mindset and design thinking can super charge technical discussions and build stronger systems. Don't rely on the user to be "smart!" It can trap you in an impossible architecture.
I'm a software engineer who spends her time writing code and developing apps. I have a pretty good grasp of the vocabulary and technologies relevant to my job. But what happens when another facet of engineering, one that is gaining a lot of traction and has a large footprint of its own starts becoming more and more relevant to my day to day tasks? Well, that's exactly what happened to me last year when DevOps became a big part of my role. This is my attempt to impart all of that knowledge onto you.
Taking advantage of AWS Parameter Store and some automation magic to make secret change management a problem of the past. We will talk about:
Resilience Engineering (RE) is both multidisciplinary field of study as well as a community of practitioner-researchers from multiple high-tempo, high-consequence domains such as aviation, medicine, power distribution, space operations, and critical infrastructure. In recent years, the world of software engineering and operations has become involved and more acquainted with this almost 20 year-old field and community. This talk will give a “lay of the land” on what RE is, what it is not, what efforts are relevant to the DevOps community, what attendees can do to learn more.