What is code?
summary
Asserts that everything around a project can be treated as code and shows concrete tooling: API surfaces generated from annotations into live docs and PDF via swagger and swagger‑to‑markup, design and manuals assembled from source with AsciiDoc and PlantUML, database migrations tracked as SQL scripts with Flyway, tests and disposable environments spun up as containers so integration tests run against real stacks using docker + arquillian (example runs take ~1 minute and pass), and Spock replaces brittle Cucumber scenarios.
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker background
- 3:16The reality of project work beyond coding
- 10:01Documentation as code and design patterns
- 16:29Operations and infrastructure as code
- 24:46Testers and quality as code
- 36:35Live coding demo introduction
- 36:56Swagger and API documentation
- 41:17AsciiDoc for project documentation
- 46:16Arquillian and Docker integration
- 53:20Challenges and closing remarks
related talks
16mcod == doc
59mEverything as a Code
50mContinuous and Automated Documentation Docs As Code in Practice
49mBottom-up Architecture: Bridging the Architecture-Code Gap
37mCode the documentation instead of documenting the code
47mCode Is Cheap. Software Isn’t.
46mSoftware Architecture vs Code
41mStop making fool of yourself about documentation