ADRs: the lost art of documenting important architectural decisions
Byte Size (INTERMEDIATE level)
Room B
Certainly, it is surprising that despite the clear benefits of architectural documentation, many software development teams still do not use them. By neglecting to document important architectural decisions, teams risk losing critical information and institutional knowledge, which can lead to problems and inefficiencies in the future.
Architectural Decision Records (ADR) can help to improve communication and collaboration between team members (which is especially valued by busy developers and architects). In this talk, we will go deeper into why ADRs are often overlooked and provide practical guidance on how to implement them effectively in your own projects.
Marek Dominiak
Sparkbyte Solutions Ltd, Trainitek
Owner of the software house, I'm a hands-on architect with 17 years of experience, mainly in the Java world. I have experience in mentoring developers and leading teams. My main focus is on creating sustainable solutions (systems that will last for many years). This set me early on the path of learning about software craftsmanship, domain-driven design, and code quality.
During my career, I have completed many small and large projects that work in production, interviewed developers, handled communication with customers, helped design architecture for entire systems and delivered them, and introduced many technologies proven in production.
I have trained hundreds of people in modern Architecture and Testing.
During my career, I have completed many small and large projects that work in production, interviewed developers, handled communication with customers, helped design architecture for entire systems and delivered them, and introduced many technologies proven in production.
I have trained hundreds of people in modern Architecture and Testing.