http://news.sciencemag.org/people-events/2014/11/physicist-w...
2,359 karma · joined May 26, 2013
http://news.sciencemag.org/people-events/2014/11/physicist-w...
http://www.parabolicarc.com/2014/10/30/apollo-ansari-hobblin...
To OP: I'm really sorry that you didn't get the job you wanted. My path is not the same as yours, but I ran into rejection applying to college, applying to grad school, and applying to jobs after grad school.
In each case I felt terrible. I didn't know how to move forwards or what I was going to do, I felt like the rejection was an indictment of my self-worth.
But I think it helps to keep three things in mind:
- The people on the other side of these interviews are humans - they make mistakes and work off incomplete data. I guarantee you that they know far less about who you are, personally or professionally, than any of your friends or loved ones.
- Your self worth isn't tied to how well you do during an interview, or how many job offers you get, or whether or not your dream company gives you a job.
- Your destination - if you don't give up, you will probably end up where you wanted to go. But almost certainly, you won't have taken the path you originally set out to take. Life is filled with unforeseen setbacks and unanticipated opportunities. Proceed with an open mind and don't feel like you need to have everything figured out right away.
I'm not a materials engineer, but I could imagine things like seasonal temperature changes, humidity, rough handling, changes in the metallurgical properties of the alloys they used over time could all affect the ability of the engine components to withstand high temperatures and pressures.
"If a man simply lets others pay for him, he is 'mean'; if he boasts of it in a jocular manner and twits his fellows with having been scored off, he is no longer 'mean' but a comical fellow. Mere cowardice is shameful; cowardice boasted of with humorous exaggerations and grotesque gestures can be passed off as funny. Cruelty is shameful— unless the cruel man can represent it as a practical joke."
I never, ever said Swift was going to be open-sourced. My only point is that, despite whatever circumstantial evidence you've cited, Apple has not decided that they don't want Swift to be open sourced.
> Also, he said they have stuff to do before the release this fall. That happened, and still not a word about it.
The fall "release" was incomplete - it didn't ship with Swift support for OS X. Presumably they've been spending the time between the fall release of Xcode 6.0 and 6.1 (which came out yesterday) working on finishing the language. Even before 6.0 was officially released they were already releasing developer previews of 6.1.
> We literally have not even discussed this [open-sourcing] yet, because we have a ton of work to do to respond to the huge volume of feedback we're getting, and have to get a huge number of things (e.g. access control!) done before the 1.0 release this fall.
If you take Chris Lattner at face value, he is saying the reason the discussion hasn't happened is because they have too much other stuff to do (as opposed to Apple being indifferent or opposed to said discussion taking place).
I do enjoy questions where there the path to the goal isn't immediately obvious, but there are immediately a couple of approaches to consider, and even though the problem itself might be novel, the steps to get there are each something a competent person can reason about.
1. China's 'reserve army of labor' hasn't necessarily been exhausted yet. Wages in the inland provinces still lag those found in the coastal provinces, and government policy is at least nominally trying to encourage investment and development there in an effort to close the gap. Smaller countries looking to jump-start their economies through export-driven industrialism may still need to compete with those provinces and should keep in mind their advantages and disadvantages (e.g. high freight costs).
2. It isn't enough for high wages alone to drive low-paying factory work out of China, Vietnam, or the other major manufacturing nations. Quality infrastructure, a reasonably well-educated workforce, political stability, etc are all contributing factors. Leaving aside the debate over whether export-driven industrialism is good or not, rising wages provide an opportunity for smaller countries to capture these jobs, but only if they take the initiative.
I'm looking to learn about how Rust's refcounting memory management works (and how it differs from how, e.g. Objective-C or Swift's runtime-based reference counting works), mostly for personal edification. Can anyone point me to any good resources?
I don't know what the state of game development support for RubyMotion is, though, so take my advice with a grain of salt.
Seeing this brought back memories. A self-contained thruster unit intended for integration into a larger robot might just have saved our project, had it been available four years ago.
I have a couple of FPGA boards sitting around. I know what my next project is going to be.
Whether or not Twitter is more or less reliable than any similar alternative doesn't really matter that much, especially if none of the alternatives offer anything more than best-effort service with no guarantee of reliability.
The fact that Twitter was (at least superficially) suitable for this sort of application was probably not intended by Twitter's developers, nor was the existence of the pathological corner case that ruined OP's fish tank anything more than a unfortunate coincidence.
It absolutely sucks that OP's fish died, but if Twitter explicitly disavows any sort of loss because of the possibility that their service might change or fail, it's doesn't seem reasonable to just ignore that and assume otherwise. Especially for an application where it doesn't matter if the service is up most of the time if it ends up failing during the brief period where it's needed the most. And if you are aware of the limitations of some aspect of your system, it then becomes possible to design redundancy into the other parts to compensate. I hope OP's next fishtank adventure keeps this in mind.
"The Twitter Entities make no warranty and disclaim all responsibility and liability for: (i) the completeness, accuracy, availability, timeliness, security or reliability of the Services or any Content; (ii) any harm to your computer system, loss of data, or other harm that results from your access to or use of the Services or any Content; (iii) the deletion of, or the failure to store or to transmit, any Content and other communications maintained by the Services; and (iv) whether the Services will meet your requirements or be available on an uninterrupted, secure, or error-free basis."
Clearly it was never meant as a reliable communications channel for any sort of M2M application where failure could result in significant economic loss or a threat to human health or life.