> But I often do need to understand why this change was made. This is the reason (and IMO the only reason) code should be commented. The why can often be hundr

> But I often do need to understand why this change was made. This is the reason (and IMO the only reason) code should be commented. The why can often be hundreds of characters explaining technical limitations at the time, business considerations, or even just "we know this will break in a non-trivial number of instances but it's an incremental step forward to our end goal so we're just doing it."