Which algorithms are worth to learn or recall on preparation to Java developer interview? [closed]?

Fizz Buzz I usually don't care, if a developer knows the basic algorithms by heart. I do care, if he is capabale of understanding requirements and translating them in correct, testable and understandable pieces of code. Ah, and I do care if he knows how to implement the most common design patterns.

And he should know when and how to use collections, threads and - String#split - it's amazing how many "developers" don't know how to read and process a simple csv file.

– Andreas_D Jan 25 at 8:44 question and solution in Fizz Buzz – bbd Jan 25 at 9:02.

Although I fully agree with Joachim comment, I would go for : collection selection. This is not an algorithm per se, but rather a good view of which collection is good for which purpose : sorted content with constant lookup time? TreeSet!

Mapped data with memorization of insertion order? LinkedHashMap! Using that, and some knowledge of design patterns behind collections, you will far too often reply to algorithms questions using the knuth answer (or the subtle variation : as long as Sun developpers implemented it correctly, I only have to choose wisely).

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.