Well-factored code often splits code out into many methods that have only one caller. It's nice to have the functionality neatly packaged into separate methods like this, but there is a downside: the reader unfamiliar with the code has to wonder: is this method here because it is called from more than one place, or is it here only for clarity? The editor could eliminate this downside and encourage refactoring into small methods by annotating a one-caller method with a gutter symbol and/or with a color. This bug replaces IDEA-3401, which was not well-formulated.