gsands

I'd say no, and let them know when/if I planned to.

Do you mean you want to sell the domain? Because streamjoy.tv doesn't seem to have anything going on at the moment.

Jerry Seinfeld on stuff (new): http://youtu.be/HfYzlSNHapA?t=1m15s

edit: start time

It is called a "zero-day" because the programmer has had zero days to fix the flaw (in other words, a patch is not available).[0]

[0] http://en.wikipedia.org/wiki/Zero-day_attack

Could be a good oculus rift controller. Very tactile.

Agreed. But am I the only one who was disappointed when not every subsequent photo after the first had movement? About half did for me.

They lose right off for me because the back button doesn't work on jet.com to even exit back to the previous site you were on.

I would fix it up.

You get 3 benefits:

1. Continued income from it (people aren't going to continue to buy it if the bad reviews keep coming in).

2. You keep/improve your reputation. If your software isn't working well for any reason at all, it can give a bad reputation to the person/company attached.

3. You increase the chances of a good buy-out in the future, over what it would currently bring now.

We all know it can be difficult to get traction on a project, not to mention paying users. You already have proved this one can get both.

Check out the Chrome extension Videostream for Google Chromecast, link: https://chrome.google.com/webstore/detail/videostream-for-go...

I actually think high level questions like these are just conversation starters which can get into highly technical conversations quickly.

Sort of like the technologies themselves; GameCenter and CoreEverything are abstractions of lower level functionality. Being able to discuss their purpose, how to use them, and how to glue them together is what a good developer is. The rest is just syntax.

I think part of the idea of interview questions like these is that it will get a developer into those finer points, if they are in a technical discussion.

I love this. For a couple of reasons.

1/I often discover new things and have new thoughts and ideas along the way of an implementation which hadn't presented themselves previously.

2/I think it's a great way to avoid overthinking a feature or arguing too much for or against it. If nearing a majority consensus (with oneself or team) and there is time to spare, add it to Version 2 -- advantages being point #1 above, and having it prepared should it be deemed worthy to be merged to Version 1. I've heard that having features in the chamber ready to release is something big corps commonly do.