16 ms·

Hi, I'm the presenter in the video. If like me you prefer text formats, I have a blog post which partially covers the same content: https://ferd.ca/operable-sof

Hi, I'm the presenter in the video. If like me you prefer text formats, I have a blog post which partially covers the same content: https://ferd.ca/operable-software.html https://ferd.ca/operable-software.html

richjdsmith 8y ago
Great video! I don't suppose there is an online version of your presentation for Tout est terrible[1] is there? I looked but couldn't find one. Ca va si c'est suelement en francais. [1]: https://ferd.ca/tout-est-terrible.html https://ferd.ca/tout-est-terrible.html
- mononcqc 8y ago
  I've looked a bit for it and it appears nobody has put it anywhere. I personally do not have a copy either. I thought CodeMesh in 2017 had it, but it was never published.
anbotero 8y ago
I actually found this presentation (and the blog post as well) quite interesting. If possible, it would be awesome for foreign people if you talked just a little bit slower: Not much, just a bit. I think you have excellent enunciation, which helps a lot already. Thanks for sharing!
- eeZah7Ux 8y ago
  What did you learn, if you don't mind sharing?
  - catwind7 8y ago
    The presenter shared his written version of the talk and i'd say that this is probably this biggest takeaway: > The important lesson is that you'll encounter multiple types of operators, with various mental models, and various approaches to your system. You must take a human-centric approach. Avoid the glass house, and provide well-layered observability probes that adapt to specific types of concerns, and provide both guidance and flexibility to operators. This will be the difference between a system where people can operate at various levels of experience, and a system where only wizards can thrive.
- kim0 8y ago
  You can actually ask YouTube to play at slower speeds, say 0.75x
irq-1 8y ago
Thanks for the text version. For the curious, here's my take-away: > The thing that you can extract from this is that generally, logs, metrics, and tracing are not provided to explain how the thing you are using works: they are meant to let you debug your usage of it. Let me repeat that and put it in bold: most applications and components you use that are easy to operate do not expose their internals to you, they mainly aim to provide visibility into your interactions with them. > This means that if you want to make your system operable, you shouldn't aim to just expose all the innards you can. You shouldn't ask people to be aware of how you've implemented things. Instead, you have to think about who is consulting the data you expose, and why. We have entire departments dedicated to User Experience (UX), but nearly no concept of Operator Experience (OX, or OpEx?) even though operators keep the lights on and are critical power users.

richjdsmith 8y ago

Great video! I don't suppose there is an online version of your presentation for Tout est terrible[1] is there? I looked but couldn't find one. Ca va si c'est suelement en francais. [1]: https://ferd.ca/tout-est-terrible.html https://ferd.ca/tout-est-terrible.html

mononcqc 8y ago
I've looked a bit for it and it appears nobody has put it anywhere. I personally do not have a copy either. I thought CodeMesh in 2017 had it, but it was never published.

anbotero 8y ago

I actually found this presentation (and the blog post as well) quite interesting. If possible, it would be awesome for foreign people if you talked just a little bit slower: Not much, just a bit. I think you have excellent enunciation, which helps a lot already. Thanks for sharing!

eeZah7Ux 8y ago
What did you learn, if you don't mind sharing?
- catwind7 8y ago
  The presenter shared his written version of the talk and i'd say that this is probably this biggest takeaway: > The important lesson is that you'll encounter multiple types of operators, with various mental models, and various approaches to your system. You must take a human-centric approach. Avoid the glass house, and provide well-layered observability probes that adapt to specific types of concerns, and provide both guidance and flexibility to operators. This will be the difference between a system where people can operate at various levels of experience, and a system where only wizards can thrive.
kim0 8y ago
You can actually ask YouTube to play at slower speeds, say 0.75x

irq-1 8y ago

Thanks for the text version. For the curious, here's my take-away: > The thing that you can extract from this is that generally, logs, metrics, and tracing are not provided to explain how the thing you are using works: they are meant to let you debug your usage of it. Let me repeat that and put it in bold: most applications and components you use that are easy to operate do not expose their internals to you, they mainly aim to provide visibility into your interactions with them. > This means that if you want to make your system operable, you shouldn't aim to just expose all the innards you can. You shouldn't ask people to be aware of how you've implemented things. Instead, you have to think about who is consulting the data you expose, and why. We have entire departments dedicated to User Experience (UX), but nearly no concept of Operator Experience (OX, or OpEx?) even though operators keep the lights on and are critical power users.