veyepar: Decoupled: Why we're reinventing a worse wheel

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:	Decoupled, headless, micro-services; Whatever you want to call it, its here to stay and often for good and great reasons. But are you using it for a good and great reason? In the past 2 years we're seen a growing emergence of decoupled builds that questionably didn't need to me. * Were they faster? * Were they more engaging? * Were they cheaper? We'll look at some the innovations that have been emerging from the frontend world and understand if this world is better or worse then the coupled delivery environment Drupal 8 is delivering. markdown
Comment:	production notes

2019-11-28/13_51_59.ts Apply: 13:59:56 - 14:21:59 ( 00:22:03 ) S: 13:51:59 - E: 14:21:59 D: 00:30:00 (Start: 477) show more...

vlc ~/Videos/veyepar/drupalsouth/drupalsouth2019/dv/huon/2019-11-28/13_51_59.ts :start-time=0477.0 --audio-desync=0

2019-11-28/14_21_59.ts Apply: 14:21:59 - 14:45:46 ( 00:23:47 ) S: 14:21:59 - E: 14:51:59 D: 00:30:00 (End: 1427) show more...

vlc ~/Videos/veyepar/drupalsouth/drupalsouth2019/dv/huon/2019-11-28/14_21_59.ts :start-time=00.0 --audio-desync=0

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