I always say more generally “explain the why”, business OR technical reasons. Bigger architecture decisions should go in ADRs (again, explain the why) but smal

I always say more generally “explain the why”, business OR technical reasons. Bigger architecture decisions should go in ADRs (again, explain the why) but smaller stuff like explaining why you monkeypatched a library can save future devs a lot of lost investigation time and pain. Maybe by the time they are reading your comment/code, the patch you wrote is supported in the main library!