Beyond Boring Text: Treating Your Architecture Documentation Like a Product

Have you ever felt like documentation is a necessary evil? Something you have to do but ultimately feels like a burden and a waste of time? If so, you're not alone—I used to feel the same way as a software architect and developer. But my attitude towards documentation changed dramatically, and I want to share why that happened.

In this talk, I’ll show you how to approach software documentation as a product rather than a burden. By treating documentation as a curated set of tools that deliver content to its audience in the most convenient way, you can create a shared understanding of your system design that fosters collaboration and communication—the ultimate goal and purpose of any documentation.

Value for the audience:
The audience will learn about my pragmatic approach to software and software architecture documentation that helps teams to create content that is useful and helps rather than wastes their time.

Problems addressed:
Creating software and software architecture documentation feels boring and like a waste of time.

The lack of software and software architecture documentation is hindering a common understanding of system design.

Documentation must:
* be accessible
* enable collaboration
* be trustworthy
* be easy to work with
* be transparent
* be alive

Talk language: English
Level: Advanced
Target group: Senior Developers, Architects, Team Leads

Company:
Lasssim - Software Architecture and Development Consulting

DI(FH) Simon Lasselsberger