You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have an understanding of what the software is about and what patterns and frameworks are used, a class' responsibility very often becomes clear by its name alone - no JavaDoc needed.
If you have an understanding of a class' responsibilities, the purpose of its methods often become very clear by their names alone - no JavaDoc needed either.
You should not have to read JavaDocs to gain understanding of a software - architecture overviews and an understanding of the domain (basically the game) are much more efficient.