One of the greatest challenges we have with any codebase is to understand its rationale.

• Why is it the way it is?
• How did it come to be this way?
• Which decisions are, therefore, decisions that need to be respected and which should be discarded as legacy?

Patterns offer a system of concepts and examples for reasoning about why code and architecture are the way they are. In recent years, inspired by patterns, architecture decision records (ADRs) have become a popular way to document and version rationale in a system. In this talk, we’ll look at the core ideas, common misconceptions and some guidelines for writing ADRs

About Kevlin

Kevlin is an independent consultant, speaker, writer and trainer. His software development interests are in programming, practice and people.

Kevlin has been a columnist for various magazines and websites. He’s a co-author of A Pattern Language for Distributed Computing and On Patterns and Pattern Languages, two volumes in the Pattern-Oriented Software Architecture series, and editor of 97 Things Every Programmer Should Know and co-editor of 97 Things Every Java Programmer Should Know.

He also writes short fiction, with a particular emphasis on flash fiction, and perform at spoken word events. He has helped organise events for National Flash-Fiction Day, the Bristol Festival of Literature and the Flash in Hand open mic evening in Bristol.

As this training is Part-Funded by the UK Shared Prosperity Fund there will be some paperwork for attendees to complete (this only needs completing once and not required for every masterclass).

This project is part-funded by the UK Government through the UK Shared Prosperity Fund. Cornwall Council has been chosen by Government as a Lead Authority for the fund and is responsible for monitoring the progress of projects funded through the UK Shared Prosperity Fund in Cornwall and the Isles of Scilly.