Hi
user
Admin Login:
Username:
Password:
Name:
Success is more than not-failing
--client
eric
--show
wtd_na_2015
--room crystal_ballroom 9733 --force
Prev: 11 Keep 'em playing
Next: (none, at end of list)
show more...
Author(s):
Heidi Waterhouse
Location
Crystal Ballroom
Date
may Tue 19
Days Raw Files
Start
16:50
First Raw Start
16:51
Duration
00:30:00
Offset
0:01:49
End
17:20
Last Raw End
17:27
Chapters
00:00
Total cuts_time
34 min.
http://lanyrd.com/2015/writethedocs/sdmpdt/
raw-playlist
raw-mp4-playlist
encoded-files-playlist
host
public
tweet
mp4
svg
png
assets
release.pdf
Success_is_more_than_notfailing.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:
We talk a lot about minimum viable products, and building our products up from small features. We talk a lot about failure, and how to learn from it and not replicate failures over and over again. But what I haven’t heard a lot of discussion about is how we know we’ve succeeded. Is it market share? Usable product? Could understanding and setting a measurable, achievable goals help us overcome imposter syndrome, second sock syndrome, and feature creep? This talk provides some metrics on identifying success, documenting what it will look like when you get there, preserving the idea, and dealing with the inevitable distractions and changes in direction that may prevent you from ending up where you expect. I plan to speak on how documentation can serve a crucial function at both defining and driving success. We need to stop believing that agile is the end of the answer and embrace it as part of building what we want to have in the end. Continuous improvement can have a victory condition, if we build it.
markdown
Comment:
production notes
2015-05-19/16_51_49.dv
Apply:
16:51:49 - 16:52:50 ( 00:01:01 )
S:
16:51:49 -
E:
16:52:50
D:
00:01:01
show more...
vlc ~/Videos/veyepar/eric/wtd_na_2015/dv/crystal_ballroom/2015-05-19/16_51_49.dv :start-time=00.0 --audio-desync=0
Raw File
Cut List
16:51:49
seconds: 0.0
Wall: 16:51:49
Duration
00:01:01
16:52:50
seconds: 0.0
Wall: 16:51:49
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
2015-05-19/16_52_51.dv
Apply:
16:52:51 - 17:27:06 ( 00:34:15 )
S:
16:52:51 -
E:
17:27:06
D:
00:34:15
show more...
vlc ~/Videos/veyepar/eric/wtd_na_2015/dv/crystal_ballroom/2015-05-19/16_52_51.dv :start-time=00.0 --audio-desync=0
Raw File
Cut List
16:52:51
seconds: 0.0
Wall: 16:52:51
Duration
00:34:15
17:27:06
seconds: 0.0
Wall: 16:52:51
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
2015-05-19/16_51_49.dv
2015-05-19/16_52_51.dv
Veyepar
Video Eyeball Processor and Review