home.social

#softwarediagraming — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #softwarediagraming, aggregated by home.social.

  1. Jacqui Read @tekiegirl ·

    avoid mixing levels of abstraction.

    But can you take this too far? Absolutely. It is usually adequate to split a high-level criterion into no more than 3-4 lower-level criteria, but as usual it depends on the scope and complexity of your ADR.

    What has worked best for you?

    I’ll be sharing more on , , and so if you got value from this post please 🔔 follow and 🔗 share.

    (Image from my book, Communication Patterns, @OReillyMedia).
    5/5

    #softwarearchitecture #adrs #softwarediagraming
  2. Jacqui Read @[email protected] ·

    avoid mixing levels of abstraction.

    But can you take this too far? Absolutely. It is usually adequate to split a high-level criterion into no more than 3-4 lower-level criteria, but as usual it depends on the scope and complexity of your ADR.

    What has worked best for you?

    I’ll be sharing more on #SoftwareArchitecture, #ADRs, and #SoftwareDiagraming so if you got value from this post please 🔔 follow and 🔗 share.

    (Image from my book, Communication Patterns, @OReillyMedia).
    5/5

    #softwarearchitecture #adrs #softwarediagraming
  3. Jacqui Read @[email protected] ·

    avoid mixing levels of abstraction.

    But can you take this too far? Absolutely. It is usually adequate to split a high-level criterion into no more than 3-4 lower-level criteria, but as usual it depends on the scope and complexity of your ADR.

    What has worked best for you?

    I’ll be sharing more on #SoftwareArchitecture, #ADRs, and #SoftwareDiagraming so if you got value from this post please 🔔 follow and 🔗 share.

    (Image from my book, Communication Patterns, @OReillyMedia).
    5/5

    #softwarearchitecture #adrs #softwarediagraming
  4. Jacqui Read @[email protected] ·

    avoid mixing levels of abstraction.

    But can you take this too far? Absolutely. It is usually adequate to split a high-level criterion into no more than 3-4 lower-level criteria, but as usual it depends on the scope and complexity of your ADR.

    What has worked best for you?

    I’ll be sharing more on #SoftwareArchitecture, #ADRs, and #SoftwareDiagraming so if you got value from this post please 🔔 follow and 🔗 share.

    (Image from my book, Communication Patterns, @OReillyMedia).
    5/5

    #softwarediagraming #adrs #softwarearchitecture
  5. Jacqui Read @[email protected] ·

    avoid mixing levels of abstraction.

    But can you take this too far? Absolutely. It is usually adequate to split a high-level criterion into no more than 3-4 lower-level criteria, but as usual it depends on the scope and complexity of your ADR.

    What has worked best for you?

    I’ll be sharing more on #SoftwareArchitecture, #ADRs, and #SoftwareDiagraming so if you got value from this post please 🔔 follow and 🔗 share.

    (Image from my book, Communication Patterns, @OReillyMedia).
    5/5

    #softwarearchitecture #adrs #softwarediagraming
  6. Jacqui Read @tekiegirl ·

    3/3
    Be careful though, some of these constraints can be sensitive topics, such as having to follow a company master solution, or that the team does not have the skills to implement an option. Keep your ADR impartial. You should assume anybody in your organisation could read it.

    I’ll be sharing more on , , and so if you got value from this post please 🔔 follow and 🔗 share.

    #softwarearchitecture #adrs #softwarediagraming
  7. Jacqui Read @[email protected] ·

    3/3
    Be careful though, some of these constraints can be sensitive topics, such as having to follow a company master solution, or that the team does not have the skills to implement an option. Keep your ADR impartial. You should assume anybody in your organisation could read it.

    I’ll be sharing more on #SoftwareArchitecture, #ADRs, and #SoftwareDiagraming so if you got value from this post please 🔔 follow and 🔗 share.

    #softwarearchitecture #adrs #softwarediagraming
  8. Jacqui Read @[email protected] ·

    3/3
    Be careful though, some of these constraints can be sensitive topics, such as having to follow a company master solution, or that the team does not have the skills to implement an option. Keep your ADR impartial. You should assume anybody in your organisation could read it.

    I’ll be sharing more on #SoftwareArchitecture, #ADRs, and #SoftwareDiagraming so if you got value from this post please 🔔 follow and 🔗 share.

    #softwarearchitecture #adrs #softwarediagraming
  9. Jacqui Read @[email protected] ·

    3/3
    Be careful though, some of these constraints can be sensitive topics, such as having to follow a company master solution, or that the team does not have the skills to implement an option. Keep your ADR impartial. You should assume anybody in your organisation could read it.

    I’ll be sharing more on #SoftwareArchitecture, #ADRs, and #SoftwareDiagraming so if you got value from this post please 🔔 follow and 🔗 share.

    #softwarediagraming #adrs #softwarearchitecture
  10. Jacqui Read @[email protected] ·

    3/3
    Be careful though, some of these constraints can be sensitive topics, such as having to follow a company master solution, or that the team does not have the skills to implement an option. Keep your ADR impartial. You should assume anybody in your organisation could read it.

    I’ll be sharing more on #SoftwareArchitecture, #ADRs, and #SoftwareDiagraming so if you got value from this post please 🔔 follow and 🔗 share.

    #softwarearchitecture #adrs #softwarediagraming