3 ms·
DAC has a lot of strengths for technical users and audiences, but it isn't accessible for everyone. Our focus is keeping everyone in the team up to date and on
by JacobDesigns 5y ago
DAC has a lot of strengths for technical users and audiences, but it isn't accessible for everyone. Our focus is keeping everyone in the team up to date and on the same page about the system design and in line documentation in an accessible, simple way. Decisions get made all the time and (most) often aren't captured in places everyone can access. Simply understanding how the product works that you're involved with shouldn't be difficult. There is a table for comparison here: https://icepanel.io/c4-model#dac-table https://icepanel.io/c4-model#dac-table
- Terretta 5y agoI don't understand, though. Since it's a model, why say "gitable=no" instead of having ability to have those "frozen sources of truth" git-committed? In fact, it's not clear to me, can I even get the model code out of this? I see "model export" but can't tell what the toolbox means from your visual tool. I really want to use this, but only if it integrates back into the everything-as-code record. (I don't even care if bi-directional for now, but it has to snapshot the model out.)
- victor96 5y agoWhat use cases do you have that need the model to be committed to the repository if it wasn't bi-directional?