The Intersection of Architecture and Implementation
summary
Argues that architecture is a first draft and must stay aligned with code by describing systems in an architecture as code ADL that generates executable structure tests (ArcUnit, NetArch, pytest equivalents) from plain rules, applied to a SysOp Squad example and refactorings like the flattening pattern. Reports generative-LM test generation success roughly 95% hit rate for Java, ~80% for C#, ~70% for Python/TS. Shows concrete checks (e.g., only persistence may reference java.sql types), fast-failing tests drive collaboration and incremental refactoring under a test-driven architecture approach.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:26Talk overview
- 3:36Architecture and implementation
- 8:13Architecture alignment
- 15:04SysOp Squad case study
- 19:59Misalignment in code
- 24:34Consequences of misalignment
- 24:54Architecture as Code
- 28:10Defining domains with Architecture Definition Language
- 32:04Collaboration friction
- 35:23Enforcing with tests
- 41:48Fast feedback changes
- 46:12Refactoring flattening
- 48:24Flattening pattern
- 53:02Collapsing components
- 1:02:49Architecture constraints
- 1:08:50Governance and collaboration
- 1:15:38Architecture as Code vision
- 1:19:53Key takeaways
- 1:20:37Q&A
related talks
58mThe Intersection of Architecture and Implementation
58m4 Key Trends Towards Better Software Architecture
44mTesting Software Architecture
51mTesting Software Architecture
49mBottom-up Architecture: Bridging the Architecture-Code Gap
22mArchitecture & ArchUnit
58mTesting Software Architecture
48mDown the Ivory Tower towards Agile Architecture