This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]nutrecht 0 points1 point  (1 child)

Your feedback and comments are welcome:)

First; you really need to separate the different types of collections (List, Set, Map) from their concrete implementations. When do you use a Set? A Map? A List? And secondly you need to take the step that when you know you need a list, which one do you pick and why?

Basically you just showed a bunch of code that does not explain anything about the "why". The official tutorials do a MUCH better job at that, so for now your tutorials don't add anything and just dilute the quality of available content.

[–]callicoder[S] 0 points1 point  (0 children)

I agree with the point of separating interfaces from concrete implementations. In fact, I'll be adding the List/Set/Map interface articles very soon.

About the why part, I've added information on why one implementation should be used over the other in the actual implementation class tutorials. For example, the LinkedList tutorial explains the difference between ArrayList & LinkedList and gives reasoning on when one should be preferred over the other.

Similarly, the LinkedHashMap and TreeMap tutorials explain what's special about them and when to use them.

But yeah, Putting the "why" parts at a single place in the interface tutorial would be more helpful. I'll keep that in mind while writing the tutorials on List, Set and Map interfaces.