Key takeaways
Hansoft dependency tracking = suck

Tuesday-Techart Bootcamp
powershell

.net modules integrated

xaml remove

SQL database interaction
com interface! for working with excel /photoshop

Rob from Bioware

pay technical debt

automate crash/errors

mandatory and thorough
code review

single point for review/dictator

Seth

cohesion/collaboration at team lvl

guide

teach

measure

trust

jason Hayes volition

working on insane

lessons in tools

tool briefs/one sheets

description

what is the main issue?

Function

how is user going to work?

justification

why is this important?

cost of solving wrong problem

understand the end user

map out artist workflow

FaceTime with user, in their shoes

dependency / downstreaming

be mindful of over-engineering

whiteboard/flowchrt: makes sense to difficult issues

Phased Development

design/implement

first iteration pass

second pass of iteration

final polish pass

phase one might be enough

Tactical

asset visual bug tracker

node based scripting python editor

interface design

separate ui from command layer

keep clicking to a minimum

clean, simple interface, consistency

intelligent grouping

polish interface

Architecture Design

minimal complexity

system

–interface
–database
–devkit