Any suggestions on learning Data structures and algorithms for java developers [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.

---

We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.

Closed 3 years ago.

开发者_运维技巧 Improve this question

What algorithms should a java developer(or maybe a better question would be a software developer in general) should know. I have Introduction to Algorithms by Cormen and Algorithms by Richard Johnsonbaugh at hand. Would going through their content be overkill?

---

from amazon data structures and algorithms in java

What algorithms should a java developer(or maybe a better question would be a software developer in general) should know.

There are no any specific Algorithms for C developers or for a Java developer. Algorithms is a "main" part of the Computer Science and here is the topic What algorithms should every developer know? and here Best source for Algorithms? and Good Data Structures text book

---

That's a very open-ended question, so a concise and useful answer is difficult. I would say that you need to know at least the data-structures and associated algorithms that Java provides in the standard libraries so that you know how and when to use each one. If you don't know the differences in structure and performance between an ArrayList and a LinkedList then you won't know when each one is appropriate. Similarly, if you don't know how a HashMap works then you can't know how to properly define classes that can be stored in one.

It's also instructive to learn a couple of different sorting and searching algorithms, for similar reasons.

---

This question here better answers what you ask.

---

It doesn't hurt to know stuff like that, but it will rarely come up*.

*Depends on what you're doing.

---

The CLRS is probably the most widely used one and reading it is definitely not overkill, just skip the proofs (I would read them just to enjoy, but not too much practical use). You may also want to check this one.