The thing that made my code 1000% more readable has been code reviews with a team that gives a damn. When reading their code I'll add feedback to parts I don't

The thing that made my code 1000% more readable has been code reviews with a team that gives a damn. When reading their code I'll add feedback to parts I don't understand (why do we need this cache invalidation, why do we use a worker pool here instead of throttling requests etc). I find that questioning sits in the back of my mind when I write code - almost like a pair coder - to the point that I try to preempt questions like this by adding it as a comment. Similarly for anything that's publicly accessible like public functions/properties/interfaces/classes, my goal for codedoc comments is to prevent the consumer (me or my team) from having to open the code to see what it does and how to consume it. If they can use it with just intellisense then it's a win. Just like code readability and design, I'm seeing comments as another tool to communicate intent that can't always be communicated by code alone.