Collection vs Collections in Java

Collection and Collections are two completely different things with confusingly similar names. Collection, singular, is an interface. It's the parent of List, Set, and Queue, and it defines methods like add, remove, size, and isEmpty. When you write Collection as a variable type, you're using this interface. Collections, plural with an s, is a utility class. It's like the Math class — you never create an instance of it, you just call its static methods. For example, Collections dot sort will sort a list for you, Collections dot unmodifiableList wraps a list so it can't be modified, and Collections dot shuffle randomizes the order. There's no inheritance relationship between them at all; Collections doesn't extend or implement Collection. They just have similar names because one is a toolbox for working with the other. A common mistake freshers make is writing Collections as a type, like Collections of String — that doesn't compile, because the interface is Collection, singular. Another mistake is not knowing the utility methods exist and writing manual loops to sort or find the maximum, when Collections dot sort and Collections dot max already do it. A nice detail to mention is that Java uses this same naming pattern elsewhere — Array versus Arrays, and Object versus Objects — where the plural version is always the static helper class. Recognizing that pattern helps you find utility methods quickly.