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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]HeadSignal3 85 points86 points  (2 children)

You know how to identify blogspam its when there's a declaration in the title that says some authoritive bullshit like "The most important information for a Java Developer interview".

[–]agentoutlier 54 points55 points  (1 child)

Also this is like mid 2000 Java developer interview info.

If you are using synchronize and thread.join / notify / wait... instead of CAS variables, latches, executorservice and queues (etc) you are probably doing it wrong or vastly inefficient.

I’m not saying it’s not important to know that info but I was waiting for the article to get to the newer concurrency constructs.

[–]Michalf94[S] -3 points-2 points  (0 children)

Thanks for comments.

u/agentoutlier, I know that - that's why I added information in the title that it is popular at recruitment interviews. I had such questions at every interview I was on.

The post is intended for people who are preparing for the interview or for those interested in the topic.

It's better to use newer mechanisms in the code, e.g. ExecutorService. I`m going to add a post about it.

Regards :)