We currently work on job that stretches out over month. Every time I look at the code, I see a lot of code and in don’t remember what decision lead to that code. there is a solution for that problem it’s an adr.

the problem is we have like 40 to 50 jobs in our repro plus 20 or more libraries. If we stuff any decision that we make about a job into the adr the adr will be flooded.

My idea is to give each library and the most complicated job their own adr directories. And then a top level adr that holds only high-level decisions including creating a new adr directory for a job or a library. I guess it technical not an architecture decision if it is only about the inner workings of one job.

I obviously would have to make sure that an adr directory is not accidentally deleted unless the job or library it descripts is deleted. Apart from this I don’t see any obvious problems with the concept. On the other hand, I have never heard of someone doing something like that and a decision like that could leave us with a mess of a documentation if not handled correctly.

Has anyone experience with something like that? Any ideas?