Removing unnecessary methods with inline code

Note: This holds only for smaller or restricted applications wherein the method logic is called at exactly one place or so. This is strict violation of object-oriented programming principles which advocate that each task or purpose should be served upon by an individual method as it warrants easy extensibility, and maintenance, apart from giving a clean picture of its job.

So, in any application, if we see that there might be future implementation change possibilities or the method is being called or may be called from multiple places in the application, then, even though if the current implementation has it that the method will be called from only one place, we have to put the logic in a separate method with an appropriate name and also mention in comment about the usage, if any.

Objective: "Put a method's logic into the body of its caller and remove the method”.
Why: Too many methods with out any real purpose, and/or many small methods, but not used in multiple places. 

Example:

// Following code returns rating for an website
// "A" for more than 1000 visits
// "B" for less than 1000 visits
String getSiteRating(){
 return moreThan1000Visits()?"A":"B";
}

boolean moreThan1000Visits(){
// totalVisits is a static visit counter defined
// in some other part of the program
 return totalVisits > 1000;
}

Now the above code has been modified as follows to remove unnecessary method moreThan1000Visits() requirement for one time task:

String getSiteRating(){
 return (totalVisits > 1000)?"A":"B";
}

This style of code writing not only saves time and code, but also allows the JVM to use resources in other parts of the application rather than executing an avoidable method stack.