Did not realize this had started an entire thread on commenting practices. I used this exercise when I was teaching coding years ago, as an example of how pseudo-coding can help you think through a solution without writing code immediately. I encourage students to think through what the problem is and the steps they would need to solve it, then write those as comments. Then you can fill in the lines underneath the comments with actual code to make it like a "paint by numbers" exercise. In a real world scenario, I would then remove the extraneous comments and only leave ones that are necessary to explain complex or unexpected operations.

Didn't expect feedback, and wasn't asking for any.