I would put it the other way around. Docker+Vagrant is best used for deployment and hopefully it will be stable and battle-tested enough so I can use it in production.
I love the fact that once I configured the dev environment on my PC and I hit the road on the next day I can have exactly same environment on my laptop by running single line - "vagrant up". Not to mention that any dev working on the same project saves himself ton of time but not having to configure everything from scratch.
I have not taken the leap of faith yet and I am not using the docker in production but hopefully this will happen soon.
It won't be contained in China, that of we can be sure of in todays global economy. If things will continue in the same direction we can expect at least a mild recession in China. That will have a large knock-off effect on the world economy. Slower growth in China will result in a slower growth everywhere else.
I don't understand this big mystery around consciousness.
Here is my take. The brain simulates the reality. That is we don't see or hear directly but instead the electro-chemical impulses go to our brain from our eyes and our ears. Our brain is big enough to simulate ourselves. Our brain is capable of noticing that the simulation of "me" is distinct from the surrounding simulation of the reality.
Do they get paid by shares or salary? I mean is it a viable alternative to having a "job"? I see many people around sitting on multiple boards of companies.
While you will hear many negatives here I believe there are few positive outcomes.
The needs of HFT are such that technology barriers are pushed to the limits. Some of the technologies developed in the process make it back to the general public.
I wish there would be a maven for R. Hope the "Reliable R code" (RRT) can achieve a similar effect. Currently CRAN is heavily broken. Installing exactly the same version of the package will work today but might not work tomorrow.
Usually with cross-product applications you have some central domain that stands behind all of them. Just use that central domain. Eg. gmail, calendar, etc. are all behind google.
I thought I will share my idea of unique, memorably passwords. I have a custom in-head hash function that I use to create a unique password for every single website where I have an account.
It works as follow, let's assume this is the domain we try to generate the password for:
www.example.com
The hash process:
1 - take first letter, move 2 in alphabet, capitalize - 2 places after e in alphabte is g ("abcdefg"), capitalize - G
2 - calculate number of words in domain, x2 = 7x2=14
3 - use standard salt - eg. tlpWENT2m
4 - take last letter - e
That leads to a password:
G14tlpWENT2me
Which is both easy to remember and allows you to have a unique hashed password for every website around.
Have fun with discovering your own hashing method.
Very interesting. Let's not forget that butter production in Bangladesh and U.S. cheese production, and sheep population in Bangladesh correlates hightly (99%) with the movements of the S&P 500.
It is worth noting GCE is more expensive now that AWS was back in 2011.
According to Netflix article the AWS experiment did run at a cost $561 per 2h, that is ~$280 per hour. Perhaps they were not utilized the cluster fully in those 2h in which case we should multiply the 1h test that performed 500k inserts per second, in that case the cost would be $182*2 = ~$365 per 1h.
GCE test did run at the cost of $330 per hour. Give or take few dollars difference if anything it's surprising GCE can do at roughly the same cost what AWS was capable of 2+ years ago.
Saying all that GCE guys did a great effort. I wonder though how much speed you can squeeze from AWS and at what cost now when AWS is sporting SSD disks.
Rather than hacking all the individual cars, hack the Tesla server and push the updates. Happened few times to open source software.