I’ve been on a few teams that create a top level folder called “decisions” in the repository. Each Architecture decision record (ADR) is in a short, numbered ma

I’ve been on a few teams that create a top level folder called “decisions” in the repository. Each Architecture decision record (ADR) is in a short, numbered markdown file in that directory. We only did this for things that are hard earned lessons or thing that the usual tests don’t communicate well. Some groups are also using “Aha!” In addition to the traditional issue tracker/backlog. Though I find its UI really confusing to use. Aside from that, do you have a moment to talk about our lord and savior pair programming and XP to foster shared code ownership and share context...?