Author(s):	Tessa Bradbury
Location	C2
Date	jan Tue 22	Days Raw Files
Start	11:40	First Raw Start	11:12
Duration	0:40:0	Offset	0:27:08
End	12:20	Last Raw End	12:23
Chapters	00:00 0:02:20 0:32:20
Total cuts_time	32 min.

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

assets release.pdf JIT_Learning_Its_great_until_it_isnt.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:	Just-in-time learning, the act of learning when you need it rather than spending weeks/months/years on it up front, is part and parcel of modern software development. It's how we make it though the ever-changing industry we're in and how we make use of all the abstraction layers we have. But does it really work for everything? Drawing on specific stories from my first few years as a software developer, we'll explore some of the underlying assumptions of JIT learning, some notable instances where it falls apart and some ways of addressing those issues. markdown
Comment:	production notes