Aaditya Deshmukh

I am a sucker of niche tools which are not as popular their other alternatives, but they get the work done just fine, or in some cases even better.

While building a product, we make some decisions that are best suited at the moment. Some of them might have some trade-offs. When we look back at the code or that particular way of execution, we might not remember why we did it that way. I have been reading that maintaining documentation is an excellent way to deal with this. Do you maintain such documentation? How do you keep track of these thought processes?