veyepar: Scalable code design with slimmer django model and more

Hi user

Admin Login:

Name: Scalable code design with slimmer django model and more
--client big_apple_py --show pygotham_2016 --room Room_CR5 11102 --force
Prev: 11 Creating a BitTorrent Client using Asyncio
Next: 11 Advanced Permissioning

show more...

Author(s):	Dawa Sherpa
Location	Room CR5
Date	jul Sat 16	Days Raw Files
Start	13:45	First Raw Start	12:59
Duration	00:25:00	Offset	0:45:34
End	14:10	Last Raw End	14:29
Chapters	00:00
Total cuts_time	19 min.

https://2016.pygotham.org/talks/248/scalable-code-design-with-slimmer-django-model-and-more
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

final audio

assets release.pdf Slimmer_models_for_more_scalable_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:	When you first start your Django project, adding functionality to your model comes really easy, because IT IS really easy to do so. However, as your application size grow, the code you end up might not be easy to work on anymore. As engineers, we should pay attention to scalability not only in terms of number of requests your server can handle, but also how your application can grow with more features, and more engineers working on it. Code scalability is the ability to grow, modify, adopt your code without a major refactor, lets say every 6 months with many people working on it at the same time. While I know that it is really hard to predict the future needs, and designing for future proof architecture blindly is a waste of time and effort, I do see the need for some forethought when you put together a solution. A good balance between current need and future need can be achieved without sacrificing a lot of productive time. Common smells that indicate you do not have scalable code design are : * Engineer cannot gain insight into what the code is doing by quickly reading the code ( bug introduction because of mis-understanding ) * Engineer cannot confidently make change to small area of the code (productivity delay, bug introduction ) * Engineer cannot easily evolve the data structure to support new use cases * Engineer cannot easily to test, modify isolated business logic All the the above are usually seen when you have a big Django model file with each model having multiple functionality. I would like to review some basic principles to help us build a scalable software system. markdown
Comment:	12_59_26.ts - venue audio feed broken till 4:44 1672930_DMOICT Open Camps CR5 130PM-530PM 16 JULY 16.mov.mp4 talk starts 20:37 production notes

2016-07-16/12_59_26.ts Apply: 13:04:10 - 13:23:56 ( 00:19:46 ) S: 12:59:26 - E: 13:29:25 D: 00:29:59 (Start: 284) (End: 1470.562333) show more...

vlc ~/Videos/veyepar/big_apple_py/pygotham_2016/dv/Room_CR5/2016-07-16/12_59_26.ts :start-time=0284.0 --audio-desync=0

	Raw File	Cut List
	12:59:26		seconds: 284.0 Wall: 13:04:10
Duration	00:29:59
	13:29:25		seconds: 1470.562333 Wall: 13:23:56
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

audio viz

2016-07-16/13_29_26.ts Apply: 13:29:26 - 13:59:26 ( 00:30:00 ) S: 13:29:26 - E: 13:59:26 D: 00:30:00 show more...

vlc ~/Videos/veyepar/big_apple_py/pygotham_2016/dv/Room_CR5/2016-07-16/13_29_26.ts :start-time=00.0 --audio-desync=0

	Raw File	Cut List
	13:29:26		seconds: 0.0 Wall: 13:29:26
Duration	00:30:00
	13:59:26		seconds: 0.0 Wall: 13:29:26
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

audio viz

2016-07-16/13_59_26.ts Apply: 13:59:26 - 14:23:41 ( 00:24:15 ) S: 13:59:26 - E: 14:29:25 D: 00:29:59 (End: 1455.0) show more...

vlc ~/Videos/veyepar/big_apple_py/pygotham_2016/dv/Room_CR5/2016-07-16/13_59_26.ts :start-time=00.0 --audio-desync=0

	Raw File	Cut List
	13:59:26		seconds: 0.0 Wall: 13:59:26
Duration	00:29:59
	14:29:25		seconds: 1455.0 Wall: 14:23:41
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

audio viz

2016-07-16/13_59_26.ts Apply: 14:23:41 - 14:28:49 ( 00:05:08 ) S: 13:59:26 - E: 14:29:25 D: 00:29:59 (Start: 1455.0) (End: 1763.0) show more...

vlc ~/Videos/veyepar/big_apple_py/pygotham_2016/dv/Room_CR5/2016-07-16/13_59_26.ts :start-time=01455.0 --audio-desync=0

	Raw File	Cut List
	13:59:26		seconds: 1455.0 Wall: 14:23:41
Duration	00:29:59
	14:29:25		seconds: 1763.0 Wall: 14:28:49
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

audio viz

2016-07-16/13_59_26.ts Apply: 14:28:49 - 14:29:25 ( 00:00:36 ) S: 13:59:26 - E: 14:29:25 D: 00:29:59 (Start: 1763.0) show more...

vlc ~/Videos/veyepar/big_apple_py/pygotham_2016/dv/Room_CR5/2016-07-16/13_59_26.ts :start-time=01763.0 --audio-desync=0

	Raw File	Cut List
	13:59:26		seconds: 1763.0 Wall: 14:28:49
Duration	00:29:59
	14:29:25		seconds: 0.0 Wall: 13:59:26
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

2016-07-16/12_59_26.ts
audio viz

audio viz

2016-07-16/13_29_26.ts
audio viz

audio viz

2016-07-16/13_59_26.ts
audio viz

audio viz

Veyepar Video Eyeball Processor and Review