Author(s):	Mike O'Connor
Location	C2
Date	jan Mon 21	Days Raw Files
Start	14:50	First Raw Start	14:15
Duration	0:20:0	Offset	0:34:57
End	15:10	Last Raw End	15:15
Chapters	00:00
Total cuts_time	20 min.

https://2019.linux.conf.au/schedule/presentation/258/
raw-playlist raw-mp4-playlist encoded-files-playlist host archive public tweet mp4 svg png

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

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
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:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	Clockwork is a language to describe how machines should behave. It was developed specifically to reduce the risk and cost of custom programming of short-run machines without loss of flexibility. Over several decades we have built custom machines and have built control systems using a variety of technologies, including: Z80 controller boards, C++ control software under Linux and a variety of PLC's. These technologies have had their strengths and weaknesses but overall we have found that Clockwork and its associated tools has far greater re-usability and lower per-machine development overhead than anything else we have tried. The language itself is not like other programming languages and this talk is about how we program in Clockwork. markdown
Comment:	production notes