home.social

#architecturedocumentation — Public Fediverse posts

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

fetched live
  1. Documentation becomes valuable when it helps the next person make a decision. Architecture documentation is not about recording everything. It is about explaining why something exists.

    Based on “arc42 by Example” by Gernot Starke and collaborators.
    #ArchitectureDocumentation #SoftwareArchitecture #KnowledgeSharing

    Photo by Glenn Carstens-Peters on Unsplash

  2. #SoftwareArchitecture diagrams are one of the clearest ways to communicate - whether you’re building something new or documenting existing systems for knowledge sharing and learning.

    Simon Brown’s #C4Model, featured in a 2018 #InfoQ article, is one of the most practical approaches to keeping architecture documentation simple, consistent & useful.

    This classic framework is as relevant today as ever!

    🔗 Read now: bit.ly/479pkKY

    #InfoQ20 #Diagramming #ArchitectureDocumentation #SoftwareDevelopment

  3. diagrams are one of the clearest ways to communicate - whether you’re building something new or documenting existing systems for knowledge sharing and learning.

    Simon Brown’s , featured in a 2018 article, is one of the most practical approaches to keeping architecture documentation simple, consistent & useful.

    This classic framework is as relevant today as ever!

    🔗 Read now: bit.ly/479pkKY

  4. 𝗪𝗶𝗹𝗹 𝗪𝗲 𝗦𝗼𝗼𝗻 𝗦𝘁𝗼𝗽 𝗪𝗿𝗶𝘁𝗶𝗻𝗴 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 𝗗𝗼𝗰𝘂𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻 𝗢𝘂𝗿𝘀𝗲𝗹𝘃𝗲𝘀? – 𝗔𝗻 𝗔𝗿𝘁𝗶𝗰𝗹𝗲 𝗯𝘆 𝗦𝘁𝗲𝗳𝗮𝗻 𝗭ö𝗿𝗻𝗲𝗿 🤖 Can #GenAI create and maintain #ArchitectureDocumentation for us? @StefanZoerner explores current use cases, risks, and why teams remain responsible for their documentation.

    💡 Topics:
    • GenAI & documentation
    • Docs-as-Code
    • governance & hallucinations

    Read the article 👉 t1p.de/xgjvd

    Stefan will present a German-language session on this topic at #SAF2026.

    #iSAQB #DocsAsCode

  5. 𝗪𝗶𝗹𝗹 𝗪𝗲 𝗦𝗼𝗼𝗻 𝗦𝘁𝗼𝗽 𝗪𝗿𝗶𝘁𝗶𝗻𝗴 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 𝗗𝗼𝗰𝘂𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻 𝗢𝘂𝗿𝘀𝗲𝗹𝘃𝗲𝘀? – 𝗔𝗻 𝗔𝗿𝘁𝗶𝗰𝗹𝗲 𝗯𝘆 𝗦𝘁𝗲𝗳𝗮𝗻 𝗭ö𝗿𝗻𝗲𝗿 🤖 Can #GenAI create and maintain #ArchitectureDocumentation for us? @StefanZoerner explores current use cases, risks, and why teams remain responsible for their documentation.

    💡 Topics:
    • GenAI & documentation
    • Docs-as-Code
    • governance & hallucinations

    Read the article 👉 t1p.de/xgjvd

    Stefan will present a German-language session on this topic at #SAF2026.

    #iSAQB #DocsAsCode

  6. #SoftwareArchitecture is never static - every architecture evolves over time.

    The real question isn’t whether change will happen, but whether that change is intentional or accidental.

    Architectural Change Cases help teams make more deliberate decisions by clarifying exactly where and how a system is expected to evolve.

    📰 Check out this #InfoQ article by Pierre Pureur & Kurt Bittner to learn more: bit.ly/3ROXMqU

    #ADR #ArchitectureDocumentation #ArchitectureEvaluation #EvolutionaryArchitecture

  7. is never static - every architecture evolves over time.

    The real question isn’t whether change will happen, but whether that change is intentional or accidental.

    Architectural Change Cases help teams make more deliberate decisions by clarifying exactly where and how a system is expected to evolve.

    📰 Check out this article by Pierre Pureur & Kurt Bittner to learn more: bit.ly/3ROXMqU

  8. 🆕 𝗪𝗵𝗮𝘁’𝘀 𝗡𝗲𝘄 𝗶𝗻 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 𝗗𝗼𝗰𝘂𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻? 𝗔𝗗𝗢𝗖 𝗖𝘂𝗿𝗿𝗶𝗰𝘂𝗹𝘂𝗺 𝟮𝟬𝟮𝟱.𝟭 𝗜𝘀 𝗛𝗲𝗿𝗲! 🎉

    The CPSA-A module ADOC - #ArchitectureDocumentation has been updated. The new version adds topics like #GenAI, Docs-as-Code, new notation options, and updated standards.

    #ADOC curator @gernotstarke shares insights into the update. 💡

    Learn what’s new and explore the updated curriculum 👉 t1p.de/37ovl

    #CPSA #AdvancedLevel #SoftwareArchitecture #iSAQB

  9. 🆕 𝗪𝗵𝗮𝘁’𝘀 𝗡𝗲𝘄 𝗶𝗻 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 𝗗𝗼𝗰𝘂𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻? 𝗔𝗗𝗢𝗖 𝗖𝘂𝗿𝗿𝗶𝗰𝘂𝗹𝘂𝗺 𝟮𝟬𝟮𝟱.𝟭 𝗜𝘀 𝗛𝗲𝗿𝗲! 🎉

    The CPSA-A module ADOC - #ArchitectureDocumentation has been updated. The new version adds topics like #GenAI, Docs-as-Code, new notation options, and updated standards.

    #ADOC curator @gernotstarke shares insights into the update. 💡

    Learn what’s new and explore the updated curriculum 👉 t1p.de/37ovl

    #CPSA #AdvancedLevel #SoftwareArchitecture #iSAQB

  10. 📁 #FromTheArchive

    The #c4Model is a way to communicate #SoftwareArchitecture at different levels of abstraction.

    You can tell different stories to different audiences - it's a way to introduce rigor & lightweight modeling to software development teams.

    Dive deeper on #InfoQ 👉 bit.ly/479pkKY

    #Diagramming #ArchitectureDocumentation #SoftwareArchitectureDiagrams

  11. 📁

    The is a way to communicate at different levels of abstraction.

    You can tell different stories to different audiences - it's a way to introduce rigor & lightweight modeling to software development teams.

    Dive deeper on 👉 bit.ly/479pkKY

  12. 📁 #FromTheArchive - The #c4Model is a way to communicate #SoftwareArchitecture at different levels of abstraction; you can tell different stories to different audiences. It's a way to introduce rigor & lightweight modeling to software development teams.

    Read on #InfoQ: bit.ly/479pkKY

    #Diagramming #ArchitectureDocumentation #SoftwareArchitectureDiagrams

  13. 📁 - The is a way to communicate at different levels of abstraction; you can tell different stories to different audiences. It's a way to introduce rigor & lightweight modeling to software development teams.

    Read on : bit.ly/479pkKY

  14. Improve your communication skills!

    🎙️Listen to the #InfoQ #podcast with Thomas Betts & Jacqui Read for insights on Communication Patterns!

    Discover how to improve communication by knowing your audience and what you need to explain to them: bit.ly/4dFfSRX

    #SoftwareArchitecture #ArchitectureDocumentation #ArchitectureDecisionRecords #DistributedTeam

  15. Improve your communication skills!

    🎙️Listen to the with Thomas Betts & Jacqui Read for insights on Communication Patterns!

    Discover how to improve communication by knowing your audience and what you need to explain to them: bit.ly/4dFfSRX

  16. In #SoftwareArchitecture, there are often no perfect solutions, only "less than perfect" alternatives that need to be balanced.

    Being able to see these choices more clearly helps current & future teams better understand the trade-offs they may have to make.

    #InfoQ article by Pierre Pureur & Kurt Bittner: bit.ly/46MjCxQ

    #ADR #ArchitectureDecisionRecords #ArchitectureDocumentation

  17. In , there are often no perfect solutions, only "less than perfect" alternatives that need to be balanced.

    Being able to see these choices more clearly helps current & future teams better understand the trade-offs they may have to make.

    article by Pierre Pureur & Kurt Bittner: bit.ly/46MjCxQ

  18. 📁 #FromTheArchive - The #c4Model is a way to communicate #SoftwareArchitecture at different levels of abstraction; you can tell different stories to different audiences. It's a way to introduce rigor & lightweight modeling to software development teams.

    Read on #InfoQ: bit.ly/3LwdlwD

    #Diagramming #ArchitectureDocumentation #SoftwareArchitectureDiagrams

  19. 📁 - The is a way to communicate at different levels of abstraction; you can tell different stories to different audiences. It's a way to introduce rigor & lightweight modeling to software development teams.

    Read on : bit.ly/3LwdlwD