Focusing on writing " comments" in your code is not an appropriate use of your time. Documenting is. The difference between comments and documentation is the difference between how and what. If your code is written using the best practices of the language you are writing in and you use common idioms and accepted models the code (and the HOW) becomes self explanatory. On occasion when you need to do something clever, unusual, or complicated that might obfuscate the intent...a brief explanation of WHAT you are doing in that block first, followed by the explanation of you cleverness (that you believe, for whatever reason, someone might not be able to decode) is in order.

One of my favorite tips for developers is "read the code". Too many developers fall into the trap of becoming lost when they don't understand some library they are using or it has a bug or edge case that is in their way. Find the source (if you can) and read it! Early in my career I would just throw my hands up when some function didn't work the way I thought it was supposed to and try to find a different solution. Luckily a Sr Dev I was working with took a look at what I was doing and found the source, opened it up and explained to me what I was doing wrong. Yeah their docs sucked, but the code doesn't lie.

Last tip - hone your debugging skills. You will spend more time debugging and maintaining code than you will writing new code. Learning the essentials rules of debugging (https://debuggingrules.com/) will aid you in your career more than following the latest trending (insert TLA here) methodology.

As for all the other tips, they more or less sound like how to be a "good" developer and get a gold star from your pointy haired boss. I guess they're good tips...I don't know...did they get you the raise? or make the code better? If so, great...I guess.