@rperezrosario@mastodon.social
Post #958348
2026-03-31 23:06 UTC
Software Patterns guru Martin Fowler sanctions (Software) Architecture Decision Records (ADRs) as a good document type to add to a software architect's arsenal.
ADR's were coined by Michael T. Nygard in this 2011 article published in a cognitek blog:
https://cognitect.com/blog/2011/11/15/documenting-architecture-decisions
TL;DR? You can get a feel for the document's structure and content here:
https://martinfowler.com/articles/building-infrastructure-platform.html#ArchitecturalDecisionRecords
"Architecture Decision Record"
https://martinfowler.com/bliki/ArchitectureDecisionRecord.html
#adr #softwaredevelopment #softwarearchitecture #documentation
Replies (1)
-
@ocratato@discuss.systems 2026-04-01 03:52
@rperezrosario Creating ADRs is a very good idea. Keeping them until they are needed is often the more difficult problem. I suggest writing them in some plain text format (Markdown for example) and storing in the same version control system you use for the source code. The same should apply to all the other design documentation.