home.social

#c4model — Public Fediverse posts

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

  1. 📁 #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

  2. 📁 #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

  3. 📁 #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

  4. 📁 #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

  5. 📁

    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

  6. 📁 #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

  7. Ever wondered how #Decathlon ensures its teams are well-equipped to make informed, strategic decisions?

    Dive into this #InfoQ #CaseStudy where we explore their use of architecture committees, the #C4Model, #SystemThinking, and #ArchitectureDecisionRecords (ADRs).

    We spoke with Raphaël Tahar to uncover Decathlon's architecture process, the challenges faced, and the organizational impacts: bit.ly/3Ah25T6

    #SoftwareArchitecture

  8. @GeePawHill
    yes, all the time.
    mostly boxes ( or rather blobs) and arrows, but i'm trying to get used to the #c4model enough to use it for casual use...

  9. 📁 #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

  10. Today, I had the opportunity to introduce the C4 model to my colleagues. I've prepared a couple of slides to share the big picture about C4. After the introduction, we've used a prepared Miro board to work on a simple Kata to practice what we've learned.

    Tomorrow, we'll use C4 to start modelling the first two layers of our software system. 🤩

    #LearningJourney #SammanCoaching #Kata #C4Model

  11. Doing a lot of strategy and high level architectural transformation at the moment. Finding text DSL based diagram generation tools for #WardleyMaps, #c4Model and #SequenceDiagrams to be super useful. Being able to version diagram content in git then just regenerate the diagrams on the fly is way more productive than working with more gui based or drawing tools. #SoftwareEngineering

  12. Today I used the with to show and explain a pretty complex change in dependencies between two systems. Turned out to be a good tool:
    - Rather quick to sketch up needed parts of the two systems architectures with the DSL
    - Could use tags to show current and desired state
    - Great reception by the audience who thought it was an excellent way to describe and communicate the change to be done