I'm not actively using it, but I'm interested to play around with this for a bit.
At work, we have architectural decision logs, for example how to structure our authentication, how to deploy services and such. Some of these decisions are fairly obvious and straightforward, but some decisions come from days and weeks of discussions between different teams and people over the past few years.
This looks like an interesting way to provide an overview of what has been considered and what the take of the group is on these different points. This would allow new people in the teams to challenge things more substantially instead of going through four steps we've been through several times already.
I don't think you ever need something like this. It's just another tool in your toolbox. It's like graphs and diagrams - at some point some information will be easier to show this way than by writing it out in details.
I've used it a few times. For example when justifying a project of migrating a large legacy app to docker deployment.
It's also useful for getting a specific kind of result from LLMs - GPT knows how to summarise discussions/conflicts in ArgDown format.
At work, we have architectural decision logs, for example how to structure our authentication, how to deploy services and such. Some of these decisions are fairly obvious and straightforward, but some decisions come from days and weeks of discussions between different teams and people over the past few years.
This looks like an interesting way to provide an overview of what has been considered and what the take of the group is on these different points. This would allow new people in the teams to challenge things more substantially instead of going through four steps we've been through several times already.