Dr. Robert Ford is that dev who made himself indispensable to the organisation by deliberately not commenting his code. He operated under the notion of those senior developers that are the physical manifestation of the documentation gatekeeping the project

@tHe-jAsE what's an example of when it's needed and when it's not? In my experience, you are more prone to under-comment than to over-comment. I obviously don't subscribe to unproductive comments but comments are an opportunity to clarify why decisions were taken, possible alternatives that didn't work, explain what a large blob of code does so a reader can get up to speed without both wasting time and risking a poor understanding of the author's intentions