I wonder if there are others using ADRs for documenting their decisions.

  • canpolat@programming.devOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    We do that in a meeting. In some cases it may take several meetings before we can make a decision. But I think those are generally fruitful meetings (I don’t see them as waste of time). PRs give people a chance to think about these on their own pace, but when it comes to decision making, I feel like meetings actually save time (provided that people are sufficiently informed).

    It’s also possible that our ADRs deal with higher level decisions and is therefore easier to establish some sort of a consensus. From your description (especially the “refactoring” bit) I thought maybe you are using ADRs at a level that is closer to code. I cannot really think of our ADRs stopping people from refactoring the code in any way :)

    • mark@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      The meetings approach is interesting. I think we did those for RFCs but I remember they were very very long and unproductive. I think the company size matters when determining the right approach.