231–240 of 322 posts
Earlier quoted context omitted.
I think you're counting the overall sphere as the volume, but water would leak in through the finger holes so only their actual material counts. I suspect different weight bowling balls generally have different volumes.
Bowling balls aren't hollow, they're solid spheres with finger holes drilled in. The varying weights comes from having weighted cores inside.
Source: as an interviewer, I had to sit in that meeting.
Once long ago when I interviewed at Apple I was asked the classic "fork in the road, two guys, one always tells the truth and one always lies" riddle, with complete earnestness as far as I could tell. Possibly the single worst interview question I've ever been asked. Of course I told the interviewer I'd heard it before and then gave the correct answer. In my case we just ended up chatting about previous experience in…
I have no idea and want the answers: Boat + bowling ball = level stays the same? Ball roll = the constant gradient is quickest?
Here's one of my old blog posts where I do the derivation:
Earlier quoted context omitted.
> I totally suck at meetings where the goal of the meeting is to make sure that everyone feels like their voice is being heard. Those are the worst. No, I don’t feel like I need to let Bob feel heard. Bob wants to create a nightmarish stack involving ElasticSearch and Kafka for a problem that grep and a flat text file could realistically handle. I have already explained to Bob that his solution is unnecessarily compl…
But is your solution scalable? Resilient against injection attacks? What about o11y? Is literally anyone besides you going to be running these searches? If so, you're going to want to put a UI around it and that means thinking about scalability, data sanitization, and o11y. Maybe Bob knows something about the scope of the problem that you don't? Look mate, software is business and business is marketing. If your solut…
I invite you to go to any Arab country and tell them to legalize gay marriage.
Earlier quoted context omitted.
>It’s an information theory question similar How would you approach it from an information theoretic sense?
In the initial state there's 24 (12 * 2) different possibilities: The marble you're looking for is one of 12 and it's either lighter or heavier. By using a balance scale there's 3 possible outcomes (left side is heavier; right side is heavier; same weight). This means that for your last (third) weighing you'll have to have reduced the problem down to 3 (or fewer) different possibilities. If there's 4 or more there's…
Earlier quoted context omitted.
In the initial state there's 24 (12 * 2) different possibilities: The marble you're looking for is one of 12 and it's either lighter or heavier. By using a balance scale there's 3 possible outcomes (left side is heavier; right side is heavier; same weight). This means that for your last (third) weighing you'll have to have reduced the problem down to 3 (or fewer) different possibilities. If there's 4 or more there's…
Now that you spell it out, I guess this just binary search. You need O(log n) weighings because each weighing splits the search space in half. So I was wrong it’s not an information theory question, it’s just comp sci algorithms. I got my college classes mixed up (it’s been 14years)
Once long ago when I interviewed at Apple I was asked the classic "fork in the road, two guys, one always tells the truth and one always lies" riddle, with complete earnestness as far as I could tell. Possibly the single worst interview question I've ever been asked. Of course I told the interviewer I'd heard it before and then gave the correct answer. In my case we just ended up chatting about previous experience in…
Here a few additional teasers, - How many golf balls fit into the plane - How many gas stations exist in country (or alternative version with city ) - How many turns do you have to go on a gum machine until colour comes out? Naturally they all evaluate properly the skills required for the job, and other professions get asked the same kind of stupid questions. Unless it is for a position I really, really want, or are…
Notes:
0 - https://www.amazon.com/dp/0316778494
1 - https://en.wikipedia.org/wiki/Fermi_problem And not the question Where are they? https://en.wikipedia.org/wiki/Fermi_paradox Same guy. At the same Los Alamos.
2 - You know, the guy who got a Nobel Prize for inventing transistors. https://en.wikipedia.org/wiki/William_Shockley
Once long ago when I interviewed at Apple I was asked the classic "fork in the road, two guys, one always tells the truth and one always lies" riddle, with complete earnestness as far as I could tell. Possibly the single worst interview question I've ever been asked. Of course I told the interviewer I'd heard it before and then gave the correct answer. In my case we just ended up chatting about previous experience in…
To which I always reply "I just start beating the crap out of one at random - the reaction of the both victim and witness will tell me which is which."
Life lesson learned for OP, when it comes to tech interviewing: (1) the riddles you already know you answer after some staged deliberation to pretend you are working it out from first principles using your genius brain (bonus points if you can work "first principles" into the conversation). (2) The riddles you don't know the answer to are the ones you say you already read in a book or online and repeat this until you…