Completed
C4 is not a design process
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
Visualise, Document and Explore Your Software Architecture
Automatically move to the next video in the Classroom when playback concludes
- 1 Introduction
- 2 Selected highlights
- 3 Moving fast in the same direction requires good communication
- 4 Why is there a separation between the logical and development views?
- 5 the architecture diagrams don't match the code
- 6 A common set of abstractions is more important than a common notation
- 7 The abstractions must reflect the technology
- 8 Think about the target audience
- 9 C4 is not a design process
- 10 retrospectively drawing diagrams
- 11 What is a "component"?
- 12 The code is the embodiment of the architecture
- 13 Is the architecture in the code?
- 14 Architecture description languages
- 15 Create an architecture description language using code
- 16 "Component Finder"
- 17 Working software comprehensive documentation
- 18 The code doesn't tell the whole story
- 19 Tribal knowledge
- 20 Product project
- 21 Microsoft Word?
- 22 Documentation should describe what the code doesn't
- 23 Tactics for better teams
- 24 The 1990's called and they want their tools back.
- 25 Do you have a ubiquitous language to describe your software?
