veyepar: The blameless post mortem: how embracing failure makes us better

Author(s):	Chris Wilcox
Location	Mystic Theatre
Date	nov Sat 02	Days Raw Files
Start	13:30	First Raw Start	13:27
Duration	0:30:0	Offset	0:02:17
End	14:00	Last Raw End	14:27
Chapters	00:00 0:26:25
Total cuts_time	26 min.

https://2019.northbaypython.org/schedule/presentation/18/
raw-playlist raw-mp4-playlist encoded-files-playlist host archive tweet mp4 svg png

assets release.pdf The_blameless_post_mortem_how_embracing_failure_makes_us_better.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:	In today’s world of developing services we tend to move fast and with that comes mistakes. This talk will discuss using post-mortems to turn incidents into opportunities for improvement, instead of just an opportunity to assign blame. While developing software, bugs and mistakes are inevitable. Come to hear how we can improve the approaches we often take as software developers to work better with one another in heated moments of failure and the aftermath of incidents. Through better interactions we can build better teams and create better services. In my career I have worked in a blameless post-mortem and a blame-full post mortem environment, across a variety of projects ranging from individual python libraries, to core infrastructure for a cloud. I am excited to share how I think not assigning blame when things go wrong results in a better team and a better product. . In today’s world of developing services we tend to move fast and with that comes mistakes. This talk will discuss using post-mortems to turn incidents into opportunities for improvement, instead of just an opportunity to assign blame. markdown
Comment:	production notes

2019-11-02/13_57_44.ts Apply: 14:00:15 - 14:00:18 ( 00:00:03 ) S: 13:57:44 - E: 14:27:43 D: 00:29:59 (Start: 151.0) (End: 154.0) show more...

vlc ~/Videos/veyepar/nbpy/nbpy19/dv/mystic/2019-11-02/13_57_44.ts :start-time=0151.0 --audio-desync=0

	Raw File	Cut List
	13:57:44		seconds: 151.0 Wall: 14:00:15
Duration	00:29:59
	14:27:43		seconds: 154.0 Wall: 14:00:18
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

Rf filename:	root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:	check and save to add this

Rf filename:

root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv

Sequence:

get this:

check and save to add this