Design Pattern summary by tech lead.
link 1. @3:00 Break programs into logically independent components, allowing component dependencies where necessary. 2. @3:10 Inspect your data objects and graph their interactions/where they flow. Keep classes simple. Keep one-way dataflow/interactions simple. @3:29 Simplicity — keep a small number of class types (controller, views, data objects) avoid creating classes that aliases those classes (managers,… Read More »