veyepar: Becoming a Better Curator of Your Code

Author(s):	Ian Zelikman
Location	Cartoon 1
Date	jul Sat 27	Days Raw Files
Start	10:30	First Raw Start	10:02
Duration	0:30:0	Offset	0:27:21
End	11:00	Last Raw End	11:02
Chapters	00:00 0:01:25
Total cuts_time	25 min.

https://www.pyohio.org/2019/presentations/119
raw-playlist raw-mp4-playlist encoded-files-playlist host archive tweet mp4 svg png

assets release.pdf Becoming_a_Better_Curator_of_Your_Code.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:	We will start the talk with an introduction to the role of a curator and how it applies to software engineers. In this talk we will discuss some principals and techniques that enable us to produce better code but applying them with the curation mindset of maintaining code quality beyond producing the next bug free feature. Some of the topics we will cover: * Promote the use of conventions and style guides for your team * Code readability matters * The first goal of writing tests should be to document the code functionality * Encourage discussion on feature implementation * Encourage discussion during code reviews * Boy Scout rule - leave the code in a better shape than which you found it * Embrace new and mature technologies, and try to incorporate them into your code when applicable At the end of the talk we will review the software curation mindset and how you can bring it to your organization. Writing code that functions correctly is only part of the development process. The majority of our time is spent reading, maintaining and refactoring our code. In this talk we will discuss how when we see our work as code curation we actually enable our job to be much easier and productive. markdown
Comment:	production notes

2019-07-27/10_02_39.ts Apply: 10:02:50 - 10:30:53 ( 00:28:03 ) S: 10:02:39 - E: 10:32:39 D: 00:30:00 (Start: 11.0) (End: 1694.0) show more...

vlc ~/Videos/veyepar/pyohio/pyohio_2019/dv/cartoon1/2019-07-27/10_02_39.ts :start-time=011.0 --audio-desync=0

	Raw File	Cut List
	10:02:39		seconds: 11.0 Wall: 10:02:50
Duration	00:30:00
	10:32:39		seconds: 1694.0 Wall: 10:30:53
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

2019-07-27/10_02_39.ts Apply: 10:30:53 - 10:31:11 ( 00:00:18 ) S: 10:02:39 - E: 10:32:39 D: 00:30:00 (Start: 1694.0) (End: 1712.0) show more...

vlc ~/Videos/veyepar/pyohio/pyohio_2019/dv/cartoon1/2019-07-27/10_02_39.ts :start-time=01694.0 --audio-desync=0

	Raw File	Cut List
	10:02:39		seconds: 1694.0 Wall: 10:30:53
Duration	00:30:00
	10:32:39		seconds: 1712.0 Wall: 10:31:11
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

2019-07-27/10_02_39.ts Apply: 10:31:11 - 10:31:14 ( 00:00:03 ) S: 10:02:39 - E: 10:32:39 D: 00:30:00 (Start: 1712.0) (End: 1715.0) show more...

vlc ~/Videos/veyepar/pyohio/pyohio_2019/dv/cartoon1/2019-07-27/10_02_39.ts :start-time=01712.0 --audio-desync=0

	Raw File	Cut List
	10:02:39		seconds: 1712.0 Wall: 10:31:11
Duration	00:30:00
	10:32:39		seconds: 1715.0 Wall: 10:31:14
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