There some cases where I like to put a short summary at the top of a class indicating what it's supposed to do, or what the scope is. Especially if (the name of) the class bears no reference to some familiar pattern in the team.
And I'm all for proper naming and method extraction to avoid comments.
We’re a place for programmers to stay up-to-date, learn new skills, and share ideas.
We’ll never post without your permission.