Skip to main content
7 events
when toggle format what by license comment
Dec 9, 2012 at 8:39 comment added Random42 @sparc_spread A programmer that explicitly states in his/her resume that s/he knows Java concurrency should know the answers (at least the last 3). Regarding the experience level, as I said, imo a programmer that claims/wishes to be architect/technical lead\senior developer and has 5+ Java experience (backend, not JSP and MVC Frameworks) should know the answers. Regarding lock vs wait/notify, locks are preferred when you really need low-level features but in most cases a higher-level alternative is available; BlockingQueue is a specially useful one.
Dec 9, 2012 at 8:32 comment added Random42 @Martijn Verburg I agree with you both; a good Java developer (especially one that says s/he knows concurrency) should know how to use wait()/notify(); at least for the curiosity on why they appear in the Object class.
Dec 9, 2012 at 3:11 comment added sparc_spread @M3th: The last person I asked these questions had 10 years of Java experience and claimed to know concurrent programming. Thanks for posting lock vs. wait/notify - I knew about lock from the Goetz book but didn't realize it was now preferred over the old way. I do agree with @Martijn though that someone with this level of experience should be aware of the older approaches. Anyway I don't mean to ask the question again (esp. since I've already marked it as answered - by you :-) ) but I would think someone with 10 years experience should be able to answer those questions, no?
Dec 9, 2012 at 3:07 vote accept sparc_spread
Dec 8, 2012 at 23:14 comment added Martijn Verburg +1 on the wait() and notify() comments - however a developer well versed in concurrency would know the history and evolution of Java's capabilities in this space (including all the way up to F&J in Java 7).
Dec 7, 2012 at 23:58 history edited Random42 CC BY-SA 3.0
added 462 characters in body
Dec 7, 2012 at 23:52 history answered Random42 CC BY-SA 3.0