will cover abstractions, naming things, building large systems from small peices, communication patterns between all the small parts, etc.
will talk about naming things for what they represent - a "schema" (psychology term, not database / xml document term) on which we build understanding
vertical slices of code, broken down in to small peices
component based development as small parts of UI - examples in backbone and maybe other frameworks