How can someone who is just learning find the commenting style that is best for them as they learn, grow, & contribute? I did a survey of programmers & will be sharing what we can do to address comment use in a way that encourages a growth mindset and empowers beginning programmers.
Every programmer has asked themselves at least once “how many comments are too many?” To the newest programmers, comments seem magical - a way of talking to yourself (or someone else!) without giving instructions to the computer. But commenting is a form of documentation/communication and engages the same vulnerability as later challenges (eg. pair programming & code review) and is likely to pique the insecurity of many programmers (especially the copy-and-paste or tutorial-level programmer)!
While most of us agree that some level of commenting is part of writing maintainable code, it’s very difficult for someone who has not yet worked in someone else’s codebase to know what is good practice and not. The answers that come back often conflict each other: Code should be DRY but well-placed comments save future devs. How can someone find the commenting style that is best for them as they learn, grow, & contribute? I did a survey of long-time industry folks, CS-majors, bootcamp grads, & hobby programmers, and I’ll be presenting my results (a few surprises here!) & sharing what we can do to address questions about comment-use in a way that encourages a growth mindset and empowers all of us.