Hacker Newsnew | past | comments | ask | show | jobs | submit | vytasgd's commentslogin

read the comment, read the article and did all the tests. Got to this one and it still freaked me out. That's crazy.


Also, for anybody who is a fan of Durandal... looks like it'll be combining with Angular:

http://eisenbergeffect.bluespire.com/angular-and-durandal-co...


I love this. Awesome. Just awesome. Seems like a great way to stay grounded and keep perspective (along with staying active and giving you structure). Keep it up.


I have a pebble for skiing (hate taking my gloves off, digging into my jacket to pull out my phone and realizing it's a text I don't even have to respond to... also can see who is calling before I answer with my earphones) and biking (quick glance rather than having to pull out my phone)

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.


I've been with you on this, but I think we are wrong. Here's where I'm at: (without foreigner's statement)

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.


Can you go into further detail about the nth abstraction of "he knows that I know..." and what effect that has on the population? The way I see it is that as soon as everybody knows that there are blue-eyed ppl and everybody knows that everybody else knows there are blue-eyed ppl the countdown begins... additionally, at that point you can already get to an infinite number of abstractions of the "he knows that I know that he.." statement because you both know that the other knows blue-eyed ppl exist, so you both know that the other knows that you know that blue-eyed ppl exist, so you both know....


Pardon? The parent's comment is correct.

Edit: my comment is still correct thanks to parent's 2nd edit.


Parent makes this very clear statement:

> The statement will have no effect when the number of blue-eyed people is 3 or more

This is wrong, and is known to be wrong. Again, if you cannot understand a problem yourself, you might at least look into it before assuming you can.


> Edit: my comment is still correct thanks to parent's 2nd edit.

If you're playing the retroactive-history game, let me point out that that edit had not been made when you made your comment. If party A issues a statement, I point out that it's nonsense, you say that you agree with party A, and then A recants, that doesn't make you right by virtue of the wording you used to agree with him. It makes you foolish.


The traveler has no effect. The logical flaw is that with n > 2 blue eyed people, everybody knows that there is at least 1 blue eyed person AND everybody knows that everybody ELSE knows that there is at least 1 blue eyed person.

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.


Just make some types more expensive. Here's a study that was showing "You get what you pay for" essentially saying that when you pay more for a wine, you get more pleasure (than if you bought that same wine for cheaper).

http://news.cnet.com/8301-13580_3-9849949-39.html


yeah weed isn't like that

if you can produce good shit, there will be a market for it

but the real startup opportunities (for now) are not in mass production


I've done very few interviews (on either side of the table) but I wish I would come across one that had two main questions in the technical interview:

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.


Ugh, coming up with something "cool" under time constraints, while someone is sitting there and watching my every move, is not exactly a realistic gauge of anything. One of the reasons the hiring process is so broken for so many is that they fail to take in to account the nervousness and pressure the candidate will invariably be feeling. Speaking as someone who has done many interviews, questions like this always make me cringe. Sitting there in a suit, sweating and angling for a job, isn't really the best time for me to come up with something "cool."


i meant this more in the sense of "what's a piece of code you've seen(or written) that made you excited and made you think 'wow that's really clever!'" It shouldn't necessarily be something earth shattering, could be very simple, just something you genuinely liked. I personally believe enthusiasm (including intellectual curiosity) is the most important quality somebody can have in the workplace.

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.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: