how to architect software?

• ~ code around user intent
• > complexity very, very bad
  • ~ even as senior developer, say "this is too complex for me"
• ~ syncable state means bugs
• ~ accessibility = allowing for wide spread
• ~ lack of completeness says "we built this for you"

Mental Models

• mostly see design patterns and ⌣ software architecture
• ⌣ locality of behavior

Specific and Nerdy

• ~ inline the invocation, but don't inline the implementation