vytasgd
http://eisenbergeffect.bluespire.com/angular-and-durandal-co...
I also lose my phone in my apartment every 5 minutes, so I can just glance at my wrist whenever i get a text and if there's a call, well, then I find my phone again.
That last one isn't a huge pain point, but the first two definitely are.
1 blue eyed person- He know's nothing, nothing happens
2 blue eyed people- Each thinks the other could be the only blue but they don't know it... deadlock.
3 blue eyed people- Each thinks the other two are caught in the 2 person deadlock scenario knowing nothing.
4 blue eyed people- Each thinks the other 3 are caught in the 3 person scenario etc...
Once the foreigner adds the knowledge:
1- he'd leave the first day
2- the second would recognize the first didn't leave, they'd both leave on day 2
3- the third would recognize the first two didn't leave on day 2, etc, etc, we were wrong...bollocks.
Edit: my comment is still correct thanks to parent's 2nd edit.
The traveler's comments would only have an effect with n<=2 blue eyed people. With n = 1, he'd instantly know. With n = 2, the 2nd blue eyed person would recognize that the first person now has the information and if he doesn't commit suicide on the first night, then the 2nd blue eyed person knows the 1st blue had the information before, meaning he saw somebody else, and then they both die on night 2. n > 2, the info is already out that blue-eyed ppl exist and the count has already started.
If your problem with the question is trying to think of a response that the interviewer would want to hear, then you aren't approaching the question correctly and/or neither is the interviewer.
1. Write some piece of code that you think is cool. It doesn't have to originally be yours, and if it would take too long to recreate exactly, write it out in pseudo code and explain how it works and why you chose it.
2. (Slightly more common, and I've asked this before) We are having Problem A, and it would be within the scope of your responsibilities. How would you approach it?
the interviewer asks follow up questions to both and hopefully learns something in the process.
Quick Bug: (Chrome on OS X, haven't checked elsewhere)for your modal (specifically modal.fade.in in bootstrap.css line 5004) you have "top:50%", which causes the very top of the modal to be cut off. Simply bumping it to 60% fixed it. Don't know if anybody else is having this same problem.
Best of luck to you!
do you have a bug-report system or anything set up? after clicking on a chart, under the div "influencers" the tooltip isn't displaying properly. (background of the tooltip might be transparent or something, I'll look into it more to figure out exactly what the problem is)
Otherwise, cool site. I'm actually working on a company that might be an interesting partnership for you. my email should be on my profile if you are interested.
http://people.scs.carleton.ca/~kranakis/Papers/urinal.pdf
NB: Haven't actually read that paper, only the abstract, I've just discussed the concept in a class...I think I might read it later today!
This is a great reminder. I feel like people typically spend too much time at the nascent stages of a venture planning everything out in their heads. There's not enough DO at this stage. They typically don't do much of anything to actually progress only to find that once they do dedicate themselves to the venture, they forget that they still need to think. Actual planning and strategerizing (it'll catch on) take a backseat to hitting deadlines. I doubt I'm the only programmer who would love a couple days to just sit down, plan, THINK, and revamp the entire architecture of their current project.