Ask HN: Architectural Decision Records

Does anyone has experience using ADRs[0] as a way of documenting your system architecture? I am currently thinking about adopting them into a project that I am about to start. ADRs can provide a 'changelog' for decisions concerning your systems architecture, they can't replace a full documentation but are comprehensive notes on why you have decided for one solution and not another one...

Every system created now is the legacy problem of someone tomorrow, so my question is: Do they actually make your job better/easier as a future maintainer of the system?

[0]: https://adr.github.io/