So you don't think that a combination of factors such as where you live, how much you get paid, relative market rates, current job market conditions, your recent payrises, your recent year end appraisal scores, where your partner works, your age, your time since last promotion or anything else the company has or can easily gain access to would be an indicator of how likely you are to leave?
I have never left a position for any of the reasons you listed. I have only left when the situation had deteriorated to the point where I couldn't stand being there another day. A toxic work environment, poor employee morale, job off-shoring, incompetent management, not promoting from within, not staffing appropriately/overwork, lack of professional growth, etc. are why I've left. By all of the metrics you listed I should have been happy.
If a company needs to use a computer algorithm to judge an employee's satisfaction with their job, then they probably don't know the employee well enough to be able to do so accurately.
The problem is that government programs often don't provide enough to help people escape poverty, or they are structured so they penalize people for saving money or getting a better job.
I would argue the best way to fight poverty is to donate money to local charities that fight poverty. We also need to be encouraging people to work hard, graduate high school and not get pregnant out of wedlock. For a great many people in poverty that's an uphill battle against cultural expectations.
There's one wait-time display for each line to go through security, so before they get in line, travelers can join the one with the shortest wait. In effect, they do their own load balancing, which can minimize the wait time for everyone.
Based on the airports I typically use I had assumed that all of them used a single line with TSA agents directing people to a particular lane. Wouldn't that be a simpler solution?
The question that was posted reads, "what can sites serving an important public function do to ensure they stay running during periods of unexpected load?"
Yes, it's total overkill for this particular case, but that wasn't what was asked.
Chicago just got busted issuing tickets for short yellows. They instructed their vendor to start ticketing vehicles that ran yellows that were only 2.9 seconds long instead of the Federally mandated 3 seconds. Please note, they did not actually change the timing of the lights, just when tickets were issued. Previously if a yellow was shorter than 3 seconds then any tickets generated were discarded. Apparently times can fluctuate slightly due to electrical issues.
How about building your tech stack so that it can be scaled up/down on-demand? I'm using Rackspace and we have dedicated servers along with cloud servers. I can add or remove cloud servers as needed and also have the load balancers updated.
If you're just doing reads against a database, it's straightforward to add additional replicas (we use MongoDB with replica sets, don't have enough data for sharding yet). If you need to do any processing, then you should build a grid compute system where you can just add additional compute nodes. We're using RabbitMQ along with Celery. Granted, this strategy ignores issues like a saturated network, but our provider is responsible for dealing with that.
Late to the party? Microsoft released a smart watch back in 2004!
http://www.cnet.com/news/time-...
http://en.wikipedia.org/wiki/S...
The hospital also waited until they got a positive Ebola test result back before taking any safety precautions. Staff were exposed for something like two days and administration resisted isolating the patient. The sample was sent through the normal channels for testing which potentially contaminated their tube system. High-risk individuals who treated Duncan were not placed in quarantine and they allowed something like 70 different people to come into contact with him. Then there's the issue of them initially prescribing antibiotics for a viral infection.
I have never understood the point of using a Bitcoin ATM versus buying through an exchange like Coinbase. It just seems like a gimmick. Why would someone on the street need to convert between fiat and cryptocurrency? If you have cash wouldn't you just pay with your cash?
Bitcoin's great for storing and transferring value. No one can take your coins without your private key and you can do international transfers yourself. Purchasing with Bitcoin, on the other hand, is not terribly practical. Not many vendors accept it compared to fiat and the confirmation times are way too long for in-person purchases.
Those guys would have been much better off spending their time and money creating Bitcoin wagering games playable over the Internet.
Thus spake the master programmer: "After three days without programming, life becomes meaningless." -- Geoffrey James, "The Tao of Programming"