I often use this style, espcially when using a special algorithm, or encoding/decoding custom file formats. This way I can use/read/write the code on the left, and quick read down the right column to see what it does.
It works great in practice, because when you're in the code, and you know what it does, your eyes don't have to dodge around extraneous documentation just to find/fix bugs. And yet, when you go back to a custom algorithm after a year of not looking at it, you can get a quick understanding of both the overview and details of the method in question.
This is actually an out-of-date image. For those of you who actually read the code, you'll notice that the IOException is not documented, and that the @throws
comment is not entirely accurate. And that's exactly what code reviews are for!