veyepar: Planning for and handling failures from open hardware, aviation, to production at Google

Author(s):	Marc MERLIN
Location	Arena
Date	jan Wed 15	Days Raw Files
Start	14:25	First Raw Start	error-in-template
Duration	0:45:0	Offset	None
End	15:10	Last Raw End
Chapters
Total cuts_time	None min.

https://lca2020.linux.org.au/schedule/presentation/24/
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Planning_for_and_handling_failures_from_open_hardware_aviation_to_production_at_Google.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

This talk will look into the failures I've encountered in multiple fields, and learned from reading from other people's failures, a common practise in aviation that has saved countless lives in not re-creating failures and accidents out of ignorance.
You will also hopefully improve your spidey sense in things that could go wrong and ask the right questions or implement the right procedures or fixes before they become necessary after downtime.
As they say in aviation "experience is a cruel teacher: she gives you the test first, and if you survive, then you get to learn the lesson".

Examples:
- how to avoid spectacular lipo fires or circuit burns
- when aviation goes wrong, from AF447, QF32, Boeings 737 Max, and more
- failures and avoiding failures in production at Google, including how automation can go wrong
- why mkdir -p 0755 /path/to/dir can take you down hard
- you know binary drivers suck, but do you need more examples? If so, come on by
- why this temporary fix will bite you hard soon after
- a problem is not actually fixed until it's root caused

Comment:

production notes