Lesson 55 - Architecture Decision Records
In this lesson Mark Richards describes Architecture Decision Records (ADRs), a great (and necessary) tool for documenting the decisions you make as an architect. You can learn more about ADRs by going to Michael Nygard’s blogpost at http://thinkrelevance.com/blog/2011/1.... Stay tuned each Monday for more lessons in Software Architecture at https://www.developertoarchitect.com/....

▶︎
Lesson 54 - The Software Architects Bookshelf

▶︎
Architecture Decision Records (ADR) as a LOG that answers "WHY?"

▶︎
SATURN 2017 Talk: Architecture Decision Records in Action

▶︎
Communicating and documenting architectural decisions - David Ayers | #LeadDevNewYork

▶︎
Lesson 112 - Architecture Characteristics Worksheet

▶︎
Architectural Decision Records (ADR): What They Are and How Architects Should Use Them

▶︎
Lesson 141 - Managing Architecture Decisions

▶︎
ADRs: the lost art of documenting important architectural decisions by MAREK DOMINIAK

▶︎
Lesson 164 - Service Oriented Architecture

▶︎
Architecture Decision Records (ADR) - The Basics

▶︎
Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker

▶︎
Train Your Brain to Never Forget (5 Feynman Habits)

▶︎
Lesson 210 - Architecture Definition Language

▶︎
How To Think SO CLEARLY People Assume You're A Genius

▶︎
Using Architecture Decision Records – Jonathan Wolski

▶︎
10 Years of Software Architecture: Best And Worst Decisions

▶︎
Ex-Google Recruiter Explains Why "Lying" Gets You Hired

▶︎
Architecture Decision Records - How not to get lost in the past by KRISZTIAN PAPP

▶︎
Understanding the differences between modularity and granularity | by Mark Richards | #GSAS22

▶︎
