With the parting comment in mind, that there are people who give a shit at FB, how do you/they reconcile putting a lot of effort into managing user envy, when we have a much bigger problem caused by FB, in that it is actively feeding a single perspective to each user to further entrench that viewpoint (with the objective of selling advertising) when it could achieve a lot more worldly good by providing alternate viewpoints. The practice of pushing more alt right to the alt rights, or more leftist content to liberals is strengthening tribalism and as a result doing far more damage to society than 'like envy' would ever do. Please don't see this as a challenge or an attack, I'm really curious to know how this sits with FB employees, climate change is threatening the planet but tribalism is threatening democracy and FB is feeding that monster.
This thing about Google preventing Firefox from using some features (Edge as well I believe) - I'm assuming this is all done using the user agent header? or are they detecting Chrome through another means. I guess I'm wondering how effective spoofing the user agent header would be in resolving that.
I failed my amazon whiteboard interview, I couldn't write a flawless binary search and as a result the guy said my entire CV must be a lie. There was a bug in the code somewhere, couldn't figure it out without a compile and a debug run. I've been coding for 38 years and I've built a world class product but hey, whiteboards don't lie right? Personally I think it was the fact that I was dealing with a lot at the time, personal stuff, plus I was banging my head against the wall trying to figure out why my socket server wasn't scaling properly to serve a large network, and I was nervous as heck.
If you want a developer who can rattle of a computer science algorithm, then whiteboard interviews are the way to go. I would rather ask the developer how she would create a password authentication scheme, and in doing so potential avoid a data breach down the line when they fail to apply proper security principles. Or I would challenge them on how they normally approach a problem, so that I could see how teachable they are. People who are not teachable are bad for business. I would also ask them to share a technique with me to see how willing to share information they are because IT people who don't like to share information are equally bad for business.
Lastly 'culture fit' is about finding more drinking buddies, if that's what you're hiring manager is doing you should fire him asap.
Thanks, I initially saw the article title as 'Apollo 10 Stopped just 47 feet from the Moon' and I thought, gee that's rather strange, why would you do that. Also, how would you do that. Thanks for saving me from embarrassment. [edit] I always read the comments before the article.
Even assuming no obstacles, gravitational perturbations due to irregularities in the distribution of the moon's mass would upset the orbit and cause a crash.
Nevertheless, there's a short story from the SF golden age exactly featuring a satellite orbiting a few feet off the ground. Including perfectly drilled tunnels in the elevations ...
You couldn't get into a circular orbit that was always 47 feet from the surface. That's impossible anyway, because a great circle route across the moon's surface is not a perfect circle, it dips down into craters and up over mountains. But could you achieve a stable elliptical orbit whose lowest approach to the surface was 47 feet? It sounds plausible to me, if not particularly safe.
Netflix does have people from MySpace, which could explain the annoying auto play feature, but the reality is Netflix has a mature process of AB testing. If autoplay is permanently on then it's because AB testing wills it so. ¯\_(ツ)_/¯
TV's should also have this feature. When you switch to a new channel, it should be displayed in a paused state and you should press a button on the remote to start playing.
Auto-play doesn't make sense anywhere, streaming apps, youtube, or TVs. Only crazy people expect video to auto-play in a video app.