How to teach your code to describe its own architecture
summary
Claims that code becomes the source of truth by auto‑generating architecture artifacts from tests and runtime traces, with survey numbers to justify it (68% developers enforce architecture, 84% want up‑to‑date diagrams, 81% reject current tools). Demonstrated tools: AppMap gem records runtime traces into appmap files, RSwag generates OpenAPI from specs, map Swagger converts appmaps into Swagger, and rails ERD emits schema diagrams; all run against a sample Rails fork and produce usable, reviewable docs.
AI-written summary · about
chapters (9)
- 0:00Start
- 2:44State of Software Architecture
- 10:06Dependency Map View
- 10:57Trace View
- 13:03Web Services Using Swagger Also Known as Open Api
- 14:16Generate Swagger Files
- 19:12Pluses and Minuses
- 25:55Entity Relationship Diagrams
- 26:24Rails Erd
related talks
57mVisualise, document and explore your software architecture
01h 00mVisualise, document and explore your software architecture
49mBottom-up Architecture: Bridging the Architecture-Code Gap
43mTesting Software Architectures
50mCoevolution of Architecture & Code - Closing The Gap
47mArchitecture as Code or How to Survive Legacy and Keep Your Sanity
44mAutomate your software design How far we can get and how the AI chan
47mBeyond Boring Text: Treating Your Architecture Documentation Like a Product