Better Resilience Adoption through UX

What is the work you're doing today?

I'm working for a small startup. I do UI engineering, and people think that I write JavaScript and CSS. That's the least of what I do. Partially because I work across the stack, partially because in my opinion, I work with what matters, the people. Writing code is the easy part, getting a button aligned is hard, but making sure that the button does what people expect, that the button is where people need it to be is so much more important. That's what I do. That's one of the things that's important to me.

What are the goals for your talk?

I want to talk about real world case studies. I don't want to talk about abstract concepts. I'll talk about real world case studies where a company's software got better. Usually through resiliency. And I don't mean using Kubernetes and other buzzwords, AI. They built a tool that wanted to be used, and engineers around the company said, oh, this is easy. I click the button and I get what I want. And now my software is better. One of the cases I want to talk about is just through monitoring and alerting, being able to see you get a better idea of what's going on and be alerted when things may start going haywire. It doesn't matter how powerful your metrics are if no one can access them.

What key takeaways would you like people to leave the talk with?

I think the most important thing is people walk away with is that people are the most important part of software. If the software is unusable, no one enjoys it. I want people to build tools, in my case resilience tools that are useful and make other people's days better and do that by talking to people.