3 karma · joined April 8, 2016
If they don't curb the hate speech and racism they are even closer to being cut entirely out of my life - I would think this is what they as a company has to balance vs people that are into those things and appreciate having a platform for such behavior. As of right now - I personally - would never work for a Twitter/Facebook, due to the online presences that they actively support, albeit I'm sure that talent pool is not #1 priority.
It's definitely not an easy position, and I guess it kinda shows that touting yourself as a tech company when you are really a platform for good/bad/medium ideas comes with its own set of challenges.
In NYC I can do a normal sit down lunch at $40 multiple times a week, without really batting an eye - whereas that would be painful in Denmark - on the plus side you usually have catered lunch which quality, choice and taste wise is not nearly as good, but significantly cheaper and with it being better for team work within the company.
For health care you should expect longer lines and significant delays in case you have a non-urgent issue; whereas that in NYC is something you can handle easily by setting up an appointment on Zocdoc so that you can see a specialist the next day - with it being covered by your health insurance.
On a NYC tech salary I tend to buy gadgets / items as often as I want, if the cost is below maybe $200, in Denmark that threshold is more like $60.
Vacation policies are generally substantially better in Denmark; and workload also being significantly lower.
Pros and cons
I'm a Danish citizen, with the fiancé being a US citizen - and my understanding is that it wouldn't be easy for us to live in Denmark due to us having an unreasonable burden in demonstrating attachment to Denmark vs the US (https://www.information.dk/indland/2016/07/nye-regler-famili...) --- and with the president-elect having talked about pausing legal immigration for 1-2 years it makes for pretty scary times as my employer currently is applying for PERM status for me (meaning things could be paused randomly by the president - and with no where for us to go but maybe Canada/other European countries)
Our scraper back then was light years ahead of any others, both in regards to performance (think checkpointing of program state) + accuracy of parsing and JS execution (back then the target goal was a complete emulation of IE6+, sans ActiveX (exception being various host objects such as XMLHttpRequest))
This scraper was easier programming then anything else out there (think visual domain specific programming language). 7 years after having left that company I was called into an interview at a rather big HR company, with them essentially asking me to meet and greet a group of 20 people, all of them working with an old old version of said software, that I had worked on releasing - as a team of two - many years prior. Quite the bizarre encounter telling them how to work with a product that was IE 5.5 compatible, and drawing on old legacy knowledge for said purpose.