is a comprehensive book on getting a job at a top tech company, while focuses on dev interviews and does this for PMs.
CareerCup's interview videos give you a real-life look at technical interviews. In these unscripted videos, watch how other candidates handle tough questions and how the interviewer thinks about their performance.
Most engineers make critical mistakes on their resumes -- we can fix your resume with our custom resume review service. And, we use fellow engineers as our resume reviewers, so you can be sure that we "get" what you're saying.
Our Mock Interviews will be conducted "in character" just like a real interview, and can focus on whatever topics you want. All our interviewers have worked for Microsoft, Google or Amazon, you know you'll get a true-to-life experience.
I think the above code is incorrect. If a reader blocks when the queue count was 0, then a writer puts something in the queue, the reader should be unblocked. The code above unblocks only when the queue fills to limit.
- Tall Brian November 04, 2014Calling "notifyAll()" on every Write() could be inefficient if the implementation is not tracking the number of blocked Readers(). I mean you don't want a system call on every queue Write().
[Note everything above is also true for Writers blocked on Limit, and readers need to unblock them]