43 karma · joined November 21, 2011
For another perspective as a US citizen living in Europe, getting work remotely for US company really only works in tech from what I have seen (maybe in other professions, but they are not that common). What you need is the combination of being able to work on contract, and hopefully not have to shift your hours unless you are working part time. For companies that are large, established, and have remote workers you will likely be paid at market rate for where you live. The tax situation can get complicated depending on your income level, and tax rates in most European countries are much higher than the US. Your investment options outside the US are limited, many expats retain their US banks for this reason. You won't have the benefit of a 401k contribution either. The best situation for employment is being able to invoice a company directly and get paid on a contract, not every company is willing to do this. Otherwise, worst case you would be employed by a local PEO which means for tax purposes you are a full time employee and will likely be paying more taxes than you would in the US. I think Croatia might be in the sweet-spot of countries that hasn't a decent quality of life but also low taxes for independent contractors.
Note this is just one service out of many and has very low latency requirements, and due to our slow pod start times in this case it didn't make sense to auto-scale. We are auto-scaling for other services in K8s.
> says their cost went from $290/month when running in VMs to $700/month
These numbers represent a snapshot in time where we are overprovisioning, for this service for the migration. You are correct that cost benefit here remains to be seen for this service. We are doing things like isolating services into separate node pools which may not allow us to be as efficient.
Safer and faster deploys was a huge win for us, for this service and others. This of course is compared to our existing configuration using VMs and Chef to manage them.
disclaimer: blog post author
disclaimer: blog post author
(disclaimer: blog post author)
We are not sold on using Helm however for K8s in general and are currently evaluating Tanka for some of our monitoring infrastructure. One of our engineers wrote up some notes on that here if you are curious https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issu...
shopt -s dotglob; for i in *; do echo -n "$i "; done
still isn't valid unfortunately because of the extra space at the end, maybe it should be more forgiving about that.For the ^W thing I'm not sure if it's possible to avoid it, I'll check it out.
http://jarv.org/2012/02/a-text-analysis-of-supreme-court-ora...
The two articles here by the same author are interesting for folks who are interested in more about sentiment analysis
http://streamhacker.com/2010/05/10/text-classification-senti... http://streamhacker.com/2010/06/16/text-classification-senti...