Summary
Small attention to detail is what separates a good engineer from a bad one. The ADR is a document that traces all changes made to an architecture.
An ADR is a document that explains a company’s decision to use a new database. It can be written by a developer, or a project repository, or even a notion, or JIRA. There are several conventions to follow, but you can always adapt them to what works best for you.
Using GitLab issues and linking every change to an issue branch helped us track the reasons behind changes, even months after implementation. This practice saved us countless times.
