> Only for as long as it takes you to build your personal network and resume so that you can demand the same pay elsewhere. Anchor your salary as high as possible as quickly as possible to establish what you're worth and then move.
How would I justify a Bay area salary to Dutch companies?
Also, visa sponsoring is hard. Triplebyte and the like never considered me.
> Bay area tech beaucoup bucks in flyover country is a recipe for early retirement.
Does anyone get paid bay area rates in other areas? I have never heard of this. I work remotely for a bay area company and get paid based on local rates.
Seriously. Good luck arguing for 400k total comp in Kansas or wherever when there are local engineers perhaps even senior to you who’ve been happily working for upper 5 figures all their career.
This helps. The cost of living keeps a lot of people out and there's a lot of competition for the folks that are here.
In smaller markets the same supply and demand exists, but there are far fewer options and possibly less willingness on the part of employers to compete for new hires.
A tech business in a smaller market might be growth constrained by a lack of talent and that may be fine. Tech employers in the bay area are generally under a lot of pressure to grow.
That's pretty deeply incorrect, I'm sorry. I think you mean you can rent a room in an apartment with roommates for 1K a month, which is the going rate unless you're in a luxury area.
Still nope. Several of the Brooklyn listings are scams: top link is a 4 BR for 900 in Bushwick, which speaks for itself. The others are NOT near Manhattan (these NJ spots like Newark, Montclair, even Bayonne are not considered close because of very long commute times). Gravesend is not anywhere near Manhattan. The list goes on, I just addressed page one. Streeteasy has more realistic listings.
Centralized. Jobs are found either in midtown or downtown, and subway lines feed into both. Your commute will be dependent on how much you spend to be near work, but even a non expensive area (like eastern Bed Stuy or Crown Heights) doesn't have a commute more than 40-45m. You can also be lucky enough to be able to walk to work if you don't mind living in Manhattan, and spending more for a nearby neighborhood.
GDPR adds a lot of regulatory red tape to things that were previously simple. It is not only for nefarious reasons that you might want to avoid GDPR.
Want to store logs? Now you need to make sure you're scrubbing any type of personal information from the logs. Want to use a third-party service? Now you need to make sure that you are using their GDPR-compliant plan, and that you are using their Amsterdam endpoints. Maybe you need to renegotiate your contract with them.
Yes, but if you are logging the IP for spam prevention, security tracking, etc, then you are in the clear per Article 6, section 1, point f [1].
However, you can't also use the IP for fingerprinting, ad targeting, etc, without acquiring informed consent, per section 1, point a.
You can put the IP in your security logs because that is necessary to secure the service. Just have a routine to scrub the logs once they are too old to be useful anymore.
You can't put the IP in your shadow profile database and sell it to shady marketing companies, unless the user has explicitly agreed to that.
The question isn't only whether something is personal information or not, it is also a question of what you intend to do with the data.
Article 6 establishes lawful purposes for data processing that do not require consent from the data subject. All other provisions of the GDPR (including, but not limited to, the maximum time you are allowed to hold the data) apply, since it is still Personal Data. The only way to avoid having to deal with GDPR entirely is to collect absolutely no Personal Data, which is almost impossible unless your web server has no logs.
Not exactly; it's up to the judges to decide whether IP addresses count as personal information as defined by the GDPR (in my opinion they're not, but I can see why one would think differently), so the flaw isn't as much inherent to the GDPR as to the fact that people just don't understand the internet.
While the wording of the Recital leaves some ambiguity as to whether an IP is automatically Personal Data under the GDPR, its specific call-out would make arguing that it is not difficult. This would particularly be the interpretation of American lawyers, who tend to assume that no connection is too tenuous to be held against their client by a shrewd prosecutor or regulator and will thus advise their client to treat all IPs in all situations as Personal Data.
> Want to store logs? Now you need to make sure you're scrubbing any type of personal information from the logs.
What?! I'm not allowed to store my users name, address and credit card number in my unencrypted syslogs anymore? HOW DARE THEY, THOSE DAMN BEUROCRATS!
Seriously though, while there are problems (like IP address being considered personal information, which they really aren't), the general idea is very positive. You shouldn't be able to store just any information of a person that only gave you this data for a specific purpose. Servers do get hacked, employees do abuse their access to systems and old hardware doesn't always get disposed of properly.
When I'm done using a service, I want my data gone from their servers ASAP, no buts.
If I could design a library, I would throw out all the books. I would have lots of little rooms instead of open spaces. I would toss out all the uncomfortable designer chairs and put in comfortable and ergonomic seats instead.
It would really be an office instead of a library, but I think this is what people actually want.
[Individuals] become [small teams] who turn into [big enterprises] / So [GitHub] be good to your [individuals], too