The Comment That Has Been Wrong For Two Years
Decide what you would do from the brief alone, including whether you would change anything at all. Everything below it is available, but the exercise stops working if you open it first.
A method carries // Retries 3 times with exponential backoff. It retries five times, linearly. A change two years ago altered the code and not the comment. A reviewer asks you to correct it.
Updating the comment to "Retries 5 times with linear backoff". It is now true, it took ten seconds, and the reviewer asked for exactly this. You have rebuilt the artefact that just failed: a restatement of code kept in step by nothing but attention, which will be wrong again after the next tuning change. It is now also more dangerous than it was, because a comment that has just been verified is trusted, and the next reader will use it instead of reading the code — which is the specific failure that makes stale comments worse than no comments.
Read this even if you are confident. It is here rather than behind a button because it is the answer most teams actually ship, it passes review, and the cost of it does not arrive until the change after this one.