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.
This is a clever answer!
- karuthedam July 01, 2014I think a && (result = b, 1) || (result = c) should do though.
Explanation of the syntax:
Basic idea: (result = b, 1) always evaluates to "1". Just a clever way to set "result = b" while making sure the whole expression always evaluates to "1" even when value of b is 0.
Now the explanation is simple:
1. when a != 0, only (result = b, 1) gets executed effectively setting result to b.
2. when a == 0, no matter what, (result = b, 1) and (result = c, 0) gets evaluated in that order effectively setting result to c.