Senior software engineers often use Architectural Decision Records (ADRs) to document their project.
ADRs trace all changes made to an architecture, including the change itself, its impact, and what was learned from it.
Documenting architectural decisions helps with future scalability, knowledge sharing within the team, and aiding future developers.
ADRs can follow conventions like MADR or adapt to the team's preferred format, providing context, problem statements, options, outcomes, consequences, and more.