veyepar: Writing Code for Users

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're a programmer you tend to think of solutions in terms of code. When a problem comes along your mind jolts to thoughts of potential implementations. Clever ideas. Libraries that could be leveraged. Databases that could offer interesting solutions. This is our job to think about these things. But unfortunately we're not listening. In this talk we'll look at two different approaches to building an application. First, we'll look at how a "code first, ask questions later" approach can lead to poor architecture and make developing a UI very difficult. Then we'll take a look at my proposed approach that focuses on users via UX and can be helpful in leading us to design a cohesive system that solves the right problem." markdown
Comment:	production notes

2012-10-06/15_59_46.dv Apply: 15:59:46 - 16:47:00 ( 00:47:14 ) S: 15:59:46 - E: 16:47:00 D: 00:47:14 show more...

vlc ~/Videos/veyepar/chicagowebconf/chicagowebconf2012/dv/Breakout_Room_1/2012-10-06/15_59_46.dv :start-time=00.0 --audio-desync=0

2012-10-06/16_47_25.dv Apply: 16:47:25 - 16:47:26 ( 00:00:01 ) S: 16:47:25 - E: 16:47:26 D: 00:00:01 show more...

vlc ~/Videos/veyepar/chicagowebconf/chicagowebconf2012/dv/Breakout_Room_1/2012-10-06/16_47_25.dv :start-time=00.0 --audio-desync=0

Rf filename:	root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:	check and save to add this