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.
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....
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).
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.
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.
I empathize. (With everything except the cofounders' idiocy, I absolutely love mine) I was brought in with my brother(MBA), we've been working on our web app for almost 10 months, and it's grown and morphed and changed more than we could have predicted. It's the first startup for any of us. The lack of salary is tough, particularly in silicon valley... but the ups and downs, the "best day or worst day of my life" that happens over and over, is a big part of the excitement of a startup (and also what wears me down the most). We are trying to figure out our future, and if our venture is something we can push on a little more for or if we should be getting jobs where we can work on our stuff on the side until it gains enough traction to raise capital or starts generating strong enough revenues. I'd be interested to know what you end up doing and if you ultimately have any advice... pm me when you make the decision if you feel so inclined.
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.
very cool stuff. It was a little confusing for me to get which things were actually the "playlists" versus the tracks versus the charts.
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.
Definitely part of my plan during the rest of this Thanksgiving week.
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.