veyepar: To comment or not? A data-driven look at developer attitudes toward code comments

Hi user

Admin Login:

Name: To comment or not? A data-driven look at developer attitudes toward code comments
--client pytexas --show pytx19 --room special_event_center 14721 --force
Next: 12 CUDA in your Python: Effective Parallel Programming on the GPU

show more... Marks

Author(s):	Veronica Hanus
Location	Special Event Center
Date	apr Sat 13	Days Raw Files
Start	14:40	First Raw Start	14:32
Duration	30:00	Offset	0:07:19
End	15:10	Last Raw End	15:32
Chapters	00:00 0:20:56
Total cuts_time	30 min.

https://www.pytexas.org/2019/talk/U2Vzc2lvbk5vZGU6OTQ=
raw-playlist raw-mp4-playlist encoded-files-playlist host archive tweet mp4 svg png

final audio

assets release.pdf What_makes_open_source_friendly_Lessons_from_a_beginners_tour_of_six_popular_projects.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:

markdown

Every programmer has asked themselves “how many comments are too many?” To the newest programmers, comments may seem magical--a way of documenting without giving instructions to the computer. But commenting engages the same vulnerability as more advanced challenges (i.e. pair programming & code review) and is likely to pique the insecurity of many programmers (especially the copy-and-paste or tutorial-level programmer)!

While most of us agree that commenting is part of writing maintainable code, it’s very difficult for someone who has not yet worked in a community-reviewed codebase to know what is good practice and not. The answers that come back often conflict each other: Code should be DRY, but well-placed comments save future devs. How can someone find the commenting style that is best for them as they learn, grow, & contribute? My survey of 170 long-time developers, Computer Science majors, bootcamp grads, & hobby programmers confirms some expectations and brings others into question. Join me for a data-based chat about the biggest pain points caused by our attitudes toward commenting and the steps we can take to encourage a growth mindset and empower programmers of all levels.

Comment:

production notes

2019-04-13/14_32_41.ts Apply: 14:32:41 - 14:34:52 ( 00:02:11 ) S: 14:32:41 - E: 15:02:41 D: 00:30:00 (End: 131.0) show more...

vlc ~/Videos/veyepar/pytexas/pytx19/dv/special_event_center/2019-04-13/14_32_41.ts :start-time=00.0 --audio-desync=0

	Raw File	Cut List
	14:32:41		seconds: 0.0 Wall: 14:32:41
Duration	00:30:00
	15:02:41		seconds: 131.0 Wall: 14:34:52
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

audio viz

2019-04-13/14_32_41.ts Apply: 14:34:52 - 14:41:22 ( 00:06:30 ) S: 14:32:41 - E: 15:02:41 D: 00:30:00 (Start: 131.0) (End: 521.0) show more...

vlc ~/Videos/veyepar/pytexas/pytx19/dv/special_event_center/2019-04-13/14_32_41.ts :start-time=0131.0 --audio-desync=0

	Raw File	Cut List
	14:32:41		seconds: 131.0 Wall: 14:34:52
Duration	00:30:00
	15:02:41		seconds: 521.0 Wall: 14:41:22
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

audio viz

2019-04-13/14_32_41.ts Apply: 14:41:22 - 14:41:45 ( 00:00:23 ) S: 14:32:41 - E: 15:02:41 D: 00:30:00 (Start: 521.0) (End: 544.0) show more...

vlc ~/Videos/veyepar/pytexas/pytx19/dv/special_event_center/2019-04-13/14_32_41.ts :start-time=0521.0 --audio-desync=0

	Raw File	Cut List
	14:32:41		seconds: 521.0 Wall: 14:41:22
Duration	00:30:00
	15:02:41		seconds: 544.0 Wall: 14:41:45
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

audio viz

2019-04-13/14_32_41.ts Apply: 14:41:45 - 15:02:41 ( 00:20:56 ) S: 14:32:41 - E: 15:02:41 D: 00:30:00 (Start: 544.0) show more...

vlc ~/Videos/veyepar/pytexas/pytx19/dv/special_event_center/2019-04-13/14_32_41.ts :start-time=0544.0 --audio-desync=0

	Raw File	Cut List
	14:32:41		seconds: 544.0 Wall: 14:41:45
Duration	00:30:00
	15:02:41		seconds: 0.0 Wall: 14:32:41
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

audio viz

2019-04-13/15_02_41.ts Apply: 15:02:41 - 15:12:42 ( 00:10:01 ) S: 15:02:41 - E: 15:32:40 D: 00:29:59 (End: 601.0) show more...

vlc ~/Videos/veyepar/pytexas/pytx19/dv/special_event_center/2019-04-13/15_02_41.ts :start-time=00.0 --audio-desync=0

	Raw File	Cut List
	15:02:41		seconds: 0.0 Wall: 15:02:41
Duration	00:29:59
	15:32:40		seconds: 601.0 Wall: 15:12:42
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

audio viz

2019-04-13/15_02_41.ts Apply: 15:12:42 - 15:16:52 ( 00:04:10 ) S: 15:02:41 - E: 15:32:40 D: 00:29:59 (Start: 601.0) (End: 851.0) show more...

vlc ~/Videos/veyepar/pytexas/pytx19/dv/special_event_center/2019-04-13/15_02_41.ts :start-time=0601.0 --audio-desync=0

	Raw File	Cut List
	15:02:41		seconds: 601.0 Wall: 15:12:42
Duration	00:29:59
	15:32:40		seconds: 851.0 Wall: 15:16:52
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

audio viz

2019-04-13/15_02_41.ts Apply: 15:16:52 - 15:32:40 ( 00:15:48 ) S: 15:02:41 - E: 15:32:40 D: 00:29:59 (Start: 851.0) show more...

vlc ~/Videos/veyepar/pytexas/pytx19/dv/special_event_center/2019-04-13/15_02_41.ts :start-time=0851.0 --audio-desync=0

	Raw File	Cut List
	15:02:41		seconds: 851.0 Wall: 15:16:52
Duration	00:29:59
	15:32:40		seconds: 0.0 Wall: 15:02:41
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

audio viz

Rf filename:

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

Sequence:

get this:

check and save to add this

2019-04-13/14_32_41.ts
audio viz

audio viz

2019-04-13/15_02_41.ts
audio viz

audio viz

Veyepar Video Eyeball Processor and Review