That makes sense.
As an old-school coder I agree that the more you write comments the better. So ideally every block of code should have some short or long explanation in the comment above.
But when you are working on a live and commercial project, spending so much time to polish your skills in literature during writing long comments may not be wise. The reason is not that you become irresponsible or anything, it's just you know your team. So most of the blocks are obvious and your teammates can easily read it without comments. So no need to spend your time on that, you'd better continue your work on other blocks. Of course it doesn't mean that comments completely vanish, there will always be some. And when you see one, it means that the code below is not trivial, otherwise there wouldn't be a comment.
I try to leave comments in all places where it needs an optimization/refactoring but, of course, not now. Usually when I add (N+1)th small feature. Eventually when a team member (or myself) during refactoring ran into a comment, he'll know that the code below should be read carefully, to prevent breaking something after refactor.
When you are contributing to an open source project it's a completely different story. In the Open source world a comment has a different smell. In an open source project there are lots of contributors (team members). An experienced contributor tend to write comments. And you should always look up to more experienced people than yourself.