Adam Walkowski
Seasoned software developer and architect with experience in various industries - ecommerce, real estate, online marketing and content creation. Building software commercially for 15 years. Solving communication challenges in complex systems and solutions for enterprises.
I'm a former co-founder and CEO of a technical startup in the video production industry. Filmmaker advanced in interactive video and non-linear storytelling. Speaker and program manager on international film workshops Film Spring Open. Graduated from Gdańsk University of Technology. My background is anchored in web applications, business process automation and video production.
Escaping from Documentation Debt. The Future of Continuous Architecture and System Visualizations
Why are code changes simple nowadays? Because we write code to be self-documented, use versioning to keep a whole history of changes, developed methods to test code instantly. Thus, we may change code more easily, the software development life cycle became faster and effective. These foundational techniques and 'as-code' practices are now possible to utilize in Software Architecture and System Design. Mature tools are right there, like C4 modeling tools, PlantUML, Marmaid, DSLs like CNCF Serverless Workflow, interactive diagrams, code generation with OpenAPI Generator or AsyncAPI Modelina. And because of generative AI, the agile architecture and architecture as code could be among the fastest trends of the next decade.
When dealing with large-scale software solutions, several limitations to growth may appear. One of them is outdated documentation, incomplete communication of requirements, reasons for previous decisions, or behaviors of the system's parts. As businesses extend their processes, the variety of utilized processes, teams and technologies increases rapidly. The web of dependencies grows between our services or subsystems, but more critically among various groups of stakeholders, specialists and target customer groups.
Within the lecture we will explore and evaluate specification standards like OpenAPI, AsyncAPI, OpenRPC, Arazzo. We dive into emerging text-to-diagram tools like Sequencie Diagram, PlantUML, Mermaid, more advanced D2. Also tools to automate documentation like ArchUnit, EventCatalog, Kogito, Docusaurus, Backstage from Spotify. And of course, we would touch Infrastructure as Code (IaC) and GitOps as proven weapons of automation.
Having a background of the generative documentation landscape we will go towards practices to build collective knowledge about our systems. On real-world examples we will explore use cases for automatically updated context maps from Domain-Driven Design practices. System design with Architecture as Code (AaC) and API versioning with Specification as Code (SaC) and Generative Contract Testing.
Seasoned software developer and architect with experience in various industries - ecommerce, real estate, online marketing and content creation. Building software commercially for 15 years. Solving communication challenges in complex systems and solutions for enterprises.
I'm a former co-founder and CEO of a technical startup in the video production industry. Filmmaker advanced in interactive video and non-linear storytelling. Speaker and program manager on international film workshops Film Spring Open. Graduated from Gdańsk University of Technology. My background is anchored in web applications, business process automation and video production.
Escaping from Documentation Debt. The Future of Continuous Architecture and System Visualizations
Why are code changes simple nowadays? Because we write code to be self-documented, use versioning to keep a whole history of changes, developed methods to test code instantly. Thus, we may change code more easily, the software development life cycle became faster and effective. These foundational techniques and 'as-code' practices are now possible to utilize in Software Architecture and System Design. Mature tools are right there, like C4 modeling tools, PlantUML, Marmaid, DSLs like CNCF Serverless Workflow, interactive diagrams, code generation with OpenAPI Generator or AsyncAPI Modelina. And because of generative AI, the agile architecture and architecture as code could be among the fastest trends of the next decade.
When dealing with large-scale software solutions, several limitations to growth may appear. One of them is outdated documentation, incomplete communication of requirements, reasons for previous decisions, or behaviors of the system's parts. As businesses extend their processes, the variety of utilized processes, teams and technologies increases rapidly. The web of dependencies grows between our services or subsystems, but more critically among various groups of stakeholders, specialists and target customer groups.
Within the lecture we will explore and evaluate specification standards like OpenAPI, AsyncAPI, OpenRPC, Arazzo. We dive into emerging text-to-diagram tools like Sequencie Diagram, PlantUML, Mermaid, more advanced D2. Also tools to automate documentation like ArchUnit, EventCatalog, Kogito, Docusaurus, Backstage from Spotify. And of course, we would touch Infrastructure as Code (IaC) and GitOps as proven weapons of automation.
Having a background of the generative documentation landscape we will go towards practices to build collective knowledge about our systems. On real-world examples we will explore use cases for automatically updated context maps from Domain-Driven Design practices. System design with Architecture as Code (AaC) and API versioning with Specification as Code (SaC) and Generative Contract Testing.