I would discourage this habit. The reason for all those long identifiers and our picky use of style conventions is to make the code itself as easy to read as if it were plain English. It requires some practice to mentally prefer the code to the comments, but once you have this the comments are mostly distractions that interrupt the flow of reading. Just imagine what our code would look like if we would generally put an English description before every line.

If code is very complicated, it should better be explained in the Javadoc. Inline comments are useful mainly when the code itself could easily be misunderstood by another reader (or your future self). Sometimes (rarely) it makes sense to use inline comments like section headings in long methods, but a good method name is like a one-line comment, too, so splitting code into smaller methods can achieve a similar effect that also increase code quality. One also tends to use a lot more inline comments in certain scripting languages to compensate the lack of information in the code (such as missing type information). But Java is quite the opposite.