News for hackers. Stuff that matters.
Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by pritianka on Wednesday September 19, 2018 @01:11PM (#18025761)
We actually spoke to this topic in our Series C announcement last year. If we pay the same (rather than by some measure of PPP) in every location, we are effectively discouraging applications from people who happen to be in more expensive areas. By making it about the cost of living, we make sure everyone is taken care of based on living needs. That said, we have an awesome chief culture officer who is leading efforts to make sure our comp calculator is fair and encourages people to apply.
Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by jkaplowitz on Wednesday September 19, 2018 @01:38PM (#18026017)
This system fails badly when people move between cheap and expensive cities over the course of their lives, and might need to build savings at expensive city levels when living in a cheap city.

Why not just pay everyone at the expensive city level? If you were hiring a true consultant rather than an employee or a full-time "contractor," you would pay them solely based on value delivered and the defensibility of their pricing given GitLab's business needs. Their cost of living wouldn't matter.

For employees at an all remote company, I don't see why their cost of living should matter any more than that. And applicants in expensive cities would not be dissuaded.

Additionally, the calculator's attempt to handle cost of living fails to address hot markets outside the US (hello from Montreal), treats many countries as way more homogeneous in cost of living than they really are, and gives a seemingly quite inadequate 17% adjustment for contractors. That doesn't cover legal and accounting fees, paid time off of various types, the cost and limitations in health insurance coverage attainable by one-person companies, normally employer-side retirement contributions, etc.

Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by giobox on Wednesday September 19, 2018 @03:05PM (#18026827)
I also find this methodology for paying engineers concerning.

It’s been a while since I last played with it, but I recall finding the results from gitlab’s publicly accessible regional salary calculator producing some pretty absurd results in the Bay Area.

I live 45 minutes from San Jose, and expect remuneration at levels commensurate with my title and experience for the Bay Area in general, as should anyone dealing with cost of living issues here. The gitlab calculator however thinks I should earn 35k less, which feels like a punishment for trying to live somewhere commutable that I can, you know, actually afford to buy a house large enough for a normal family.

If I live in commute range of the same location, why pay me 35 grand less? Should I apologise for my less desirable zip code?

> https://about.gitlab.com/job-families/engineering/developer/ (scroll down lots for the calculator)

Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by detaro on Wednesday September 19, 2018 @06:37PM (#18028215)
I was wondering that too (since the calculator seems to think everything in Germany outside a few large metros is supposed to cost the same, which is ... unrealistic) and found https://about.gitlab.com/handbook/people-operations/global-c...

> GitLabbers may select any metro area within one hour and forty-five minutes of their residence when determining their geographical area

Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by giobox on Wednesday September 19, 2018 @08:43PM (#18028832)
Ah that’s interesting, certainly assuages some of my concerns with this approach, and would obviously allow almost all Bay Area employees to claim the SF salary range.

Arguably the calculator should be configured to just select the maximum permissible salary range inside the permitted radius based on a home zip code, given that presumably everyone who accepts a job offer at gitlab will do this manually anyway. You’d be foolish not to.

It’s still troubling how ‘wrong’ the numbers look for various regions I’m familiar with though.

Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by mikekchar on Wednesday September 19, 2018 @10:00PM (#18029196)
I can't find their calculator currently, but last time I looked they treated all of Japan as Tokyo. It's kind of funny because although one could quibble about the salary range they give for Tokyo, if I compare it to the salary that someone would make in rural Japan (where I live), it's at least twice as much.

They've got their formula and I think it's probably fair to say that they aren't paying at the top end of the range in expensive markets. Also by scaling on cost of living, they are getting mismatches with the local market -- both up and down. But it's a formula that's intended to be transparent. As much as they say publicly that they want to be competitive in every market, the reality is that a formula will never be able to achieve that.

I quite like their system. As a developer, I can look at what they are offering and decide before I apply if they are going to be in the ballpark I'm looking at. Not everybody has to work at Gitlab. Gitlab also doesn't have to hire all the best developers in every market -- their strategy is to hire around the world. SV is the most expensive market in the world -- in many cases by 1-2 binary orders of magnitude. Remote only companies don't have to pay those prices and I don't see why they should. That Gitlab even tries to hire in expensive markets is interesting to me. I'm not really sure what value they are getting from it.

I know in the US (and especially SV) there is a feeling that expensive markets attract the best talent. In my experience this isn't really true. In my experience expensive markets attract more people, but the range of ability and experience is about the same. So you may have more great developers in absolute numbers, but your chance of hiring them (especially if you are on a budget) is not any higher at all (and in many cases quite a bit lower).

I should note, in closing, that I may be strange: I don't care at all what anyone else makes in the company. I only care if people pay me what I want to be paid. If someone else makes more, then good for them. If they make less, then that's too bad. But I don't personally care either way.

Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by dragonwriter on Wednesday September 19, 2018 @03:11PM (#18026871)
> If I live in commute range of the same location, why pay me 35 grand less?

If you are doing location-based pay at all, you can't really apply his rule because very large areas are connected by within-commute-distance links such that if you never distinguished places within commute distance by pay you'd essentially eliminate location-based-pay other than across high-friction borders or places that are (either in fact or at least for transit purposes) isolated islands.

Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by giobox on Wednesday September 19, 2018 @03:20PM (#18026935)
A fair counterpoint, but if the methodology creates results that do not reflect market reality, it’s arguably not fit for purpose. I do think that much of that can be mitigated with more sensible “region” factors, but that would greatly increase the complexity of the process. Setting remuneration fairly is a hard problem, but this is arguably not a great solution either.
Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by pritianka on Wednesday September 19, 2018 @01:40PM (#18026039)
This is really useful information. Thanks for sharing. I will put this in front of our CCO, Barbie.
Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by ahkurtz on Wednesday September 19, 2018 @02:45PM (#18026647)
So you've never heard this before or won't comment here?
Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by pritianka on Wednesday September 19, 2018 @03:45PM (#18027144)
"Additionally, the calculator's attempt to handle cost of living fails to address hot markets outside the US (hello from Montreal), treats many countries as way more homogeneous in cost of living than they really are, and gives a seemingly quite inadequate 17% adjustment for contractors. That doesn't cover legal and accounting fees, paid time off of various types, the cost and limitations in health insurance coverage attainable by one-person companies, normally employer-side retirement contributions, etc."

I, personally, did not know about the way we treat intl comp on the calculator because I do not work in people ops. I found it useful new information.

Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by ahkurtz on Wednesday September 19, 2018 @04:09PM (#18027306)
Thank you. I understand. I know PR is difficult and I really value the candor. I am very concerned personally about what Gitlab represents for my industry, but if you are all willing to speak directly to challenges on it that goes a very long way. I hope you can understand also why people have these concerns.

It seems to me that the reverse of your policy would be best for the world. If you free people to move, they can choose community, friends, family, politics over being tied to a single geographic location where most of the activity is. This would help with availability of technologists in many disadvantaged locales, and would provide an influx of taxable income and consumer spending locally. This should have the ultimate effect of improving economic conditions in depressed areas, and when that happens you can actually come back and reduce everyone's wages across all locales because the economy is healthier and more robust. It works out for the owners too in the end, if they take a long enough view.

Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by Vinnl on Wednesday September 19, 2018 @07:35PM (#18028506)
> If you free people to move

I guess it depends on your perspective whether this is the case. With the current policy, if the implementation works, GitLab employees should be free to move anywhere without sacrificing anything in terms of living conditions. If you live somewhere with low costs of living, you can move to your community in an area with higher costs of living, without noticing in the amount of things you can purchase. The same holds true when you move to an area with lower costs of living, but of course, you'd get paid less.

Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by pritianka on Wednesday September 19, 2018 @04:22PM (#18027408)
No problem at all and glad you find the candor useful. It is one of our company values to be transparent :-).

I also hear you in your concern. There is a flip side perspective to what you are saying as well where someone might be forced to uproot from their home which happens to be in a more expensive area because they would save so much elsewhere. But regardless of the specific arguments, what I have truly learned here in this thread is that we should continue the conversation in the community. I am going to sync up with the people ops org and suggest that we share our rationale in more detail in the near future and/or also incorporate the good points that were raised.

I do think it is amazing that GitLab brings these conversations to the fore because opacity has been the norm for way too long around comp and we need to change that as an industry and community.

Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by ahkurtz on Wednesday September 19, 2018 @05:36PM (#18027899)
For me, in this case, the specific arguments are exactly what matters. If your company claims a solid economic rationale they should provide one. I'm not sure how it's possible you've had this policy this long and can't come out swinging on this topic. Claiming fairness vaguely is not enough to gain goodwill. It's easy to assume greed and desire for control over employees in this remuneration policy, and I'm quite happy to make that argument if your company needs that feedback. You probably don't want people like me in your company, because I am annoying, but I do have a lot of diverse experience and an abiding concern for the health of my company and coworkers. If this policy doesn't reflect a deep level of antipathy about contributors (currently) high wages, and if the company would reverse this policy in considerance, people like me would be in the door tomorrow - thousands of us. You recently hired someone I love and deeply respect professionally, so I hope your company plans to take good care of them. They deserve it, and you do to. Everyone deserves it, especially if they can make it in the door in this new economy. I'm arguing for you too, you personally, if you can see that. End "brain-drain" in USA (and its associated economic spheres).
Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by jkaplowitz on Wednesday September 19, 2018 @02:21PM (#18026424)
Thanks!
Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by dragonwriter on Wednesday September 19, 2018 @02:03PM (#18026274)
> If we pay the same (rather than by some measure of PPP) in every location, we are effectively discouraging applications from people who happen to be in more expensive areas.

If you do location-based pay, you are even more strongly discouraging applications from people in less expensive areas, especially if you don't adjust salaries for relocations after someone is employed, since someone in a less-expensive area who might consider working for you is encouraged to delay their application, seek employment that will let them wlive in a more expensive area, and then apply to GitLab (and, if you don't do post-enployment location-based adjustments, then move back to the cheap area.)

> efforts to make sure our comp calculator is fair and encourages people to apply.

As long as you pay people differently for the same work based on where they live when they apply, your comp calculator will not be fair.

To the extent that place of residency at time of application correlates with status in any protected class, it also seems to be a pretty open and shut unlawful discrimination by disparate impact case waiting to be filed, too.

Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by DailyHN on Wednesday September 19, 2018 @02:16PM (#18026382)
So what I'm understanding is that, if I'm stuck in an awful city with low wages, Gitlab would like to prevent upward mobility so I stay there.

What does this look like when it comes to company culture? Emphasis on maintaining a "diverse" team?

Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by orf on Wednesday September 19, 2018 @02:31PM (#18026520)
Alternatively, they would offer you a fair salary what allowed you to move to a city with higher wages (and a higher cost of living).
Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by DouweM on Wednesday September 19, 2018 @06:18PM (#18028119)
Note that GitLab _does_ adjust compensation when relocating: https://about.gitlab.com/handbook/people-operations/global-c... + https://about.gitlab.com/job-families/move/

That means that as someone working at GitLab, my current wage is competitive compared to local companies, + I get all of the perks of remote work, working on open source, developer tooling, etc, and all of this will still be the case if I were to move elsewhere.

The exact amount of money deposited into my account each month would go up or down, but my lifestyle would stay roughly the same.

I know I’d make a lot more money if I lived in, say, the Bay Area, and if I made that same amount of money pretty much anywhere else I could live like a king, but I honestly don’t care. I quite like my decidedly not-king-like life today, and I love that with GitLab, I can have this same life and job wherever I choose to live.

I’m currently living in the Netherlands, but am planning to move to Mexico in a few years to be closer to my fiancée’s family. If all goes well, GitLab will travel there with us, and while my compensation will see a decrease, our life style won’t.

GitLab’s compensation philosophy is one of competing with the local market, instead of putting a fixed price on the value I or anyone else provides to the company, and that’s totally fine by me. If it wasn’t for GitLab, I’d probably be working at one of those local companies, so aren’t I still better off? For the company, it means that it/we can hire great people wherever they may be on earth, without being limited to the subset of great people who also happen to or want to live in the specific city the company happens to be based in.

This may come as a surprise to some, but there are some amazing engineers out there who have zero interest in living in the Bay Area, and who don’t particularly care about maximizing their yearly take home pay, as long as they make enough money to provide for themselves and their family, and can live in whatever city or country or continent that they prefer. The map on our team page is a testament to that: https://about.gitlab.com/team/ (mobile-friendly: https://gitlab-com.gitlab.io/teampage-map/)

FWIW, I know of colleagues who have moved to locations with both lower and higher cost of living compared to the location they were hired in, and I’ve never heard about requests to move being rejected.

Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by EduardoBautista on Thursday September 20, 2018 @09:38PM (#18036627)
I live in Mexico. With GitLab’s salary calculator, I would earn about a third of what I earn now.
Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by jabits on Wednesday September 19, 2018 @01:35PM (#18025995)
I did not know companies actually do this. I would never work for a different salary than my peers (based on location). In my small "virtual" company, most of my colleagues live and work in Wisconsin (US). I live in Hawaii, where the expenses are much higher, but I would never dream of asking for more money, and I would be laughed out of the room (virtually!). Years ago, when I was an officer in the Air Force, we all had the same salary, but the government did provide Housing Allowances. This is similar, but not the same thing. A unit of salary is for a unit of work, and I do not believe this should vary by geography. If their workers choose to live in SF vs Oklahoma or Buffalo, then they pay the price. I realize that I have less "real" wages than the rest of my team in Milwaukee or Green Bay, but Maui has its compensating benefits.
Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by 0xffff2 on Wednesday September 19, 2018 @01:41PM (#18026047)
I agree, and I think that military housing allowances (which are adjusted for CoL) also have the additional justification that (generally speaking) you don't get to choose where you are stationed. As a service member, the military tells you where to go and you go, so it makes a certain amount of sense that you're then paid enough to live there.

As a software developer in the civilian world, my physical location has nothing to do with my work, so it makes no sense for my compensation to be based on my location.

Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by 0xffff2 on Wednesday September 19, 2018 @01:36PM (#18026005)
I don't understand this rational at all. If a developer in SF is worth x dollars to you, why are they suddenly worth less if they move to a lower CoL area? If you're paying salaries that are livable in a high CoL area, you aren't discouraging people living there, you're freeing people to move wherever they want.

I'm a Silicon Valley based dev who really wishes he could move far, far away from here without taking a huge pay cut, so I'm obviously biased. That said, in my view as an employee, the value I create for the company isn't based on my physical location, so why should my salary be?

Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by jcdavis on Wednesday September 19, 2018 @01:51PM (#18026157)
> That said, in my view as an employee, the value I create for the company isn't based on my physical location, so why should my salary be

Because your salary is much more influenced by market supply and demand than the value you create for your employer.

Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by dragonwriter on Wednesday September 19, 2018 @01:56PM (#18026197)
The market for remote work isn't geographically constrained, so it doesn't make sense to make pay offers as if you were hiring in specific geographically constrained markets rather than the unconstrained remote work market.
Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by jcdavis on Wednesday September 19, 2018 @02:02PM (#18026264)
As the devils advocate: Why not? The competition for that employee is largely local offers, remote is a small part of the overall market. Plus many other companies hiring for remote do local adjustments too, they just aren't public about it.

This all sounds weird for me to say because I certainly want devs to get paid, but this is the reality of the situation

Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by ahkurtz on Wednesday September 19, 2018 @02:56PM (#18026745)
Can you name any of these non-public local adjusters? Cause all the remote workers I know make the same salary as their local counterparts.
Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by jkaplowitz on Wednesday September 19, 2018 @02:14PM (#18026370)
Agreed. Though I can imagine some companies reasonably applying constraints in certain areas: working hours overlap, travel costs, and (especially where they don't do the fraudulent "honest this person whom we treat daily like an employee is not one" contractor lie) compliance costs and obligations.

That may indirectly imply some geographical constraints which could affect the shape labor market and the resulting supply/demand math leading to a salary. But it's definitely not what most companies do in their cost of living adjustments.

Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by lordnacho on Wednesday September 19, 2018 @01:51PM (#18026154)
It's a negotiation, right? And at least some of the cards are known, such as an admittedly noisy estimate of what people will accept as a salary.

Basically the company shares in your lowered living costs if you are somewhere cheap. Hopefully they won't eat the whole savings, something should be left for both parties.

Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by ahkurtz on Wednesday September 19, 2018 @02:59PM (#18026766)
What do you think is the likely outcome here?
Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by briansteffens on Wednesday September 19, 2018 @03:45PM (#18027145)
I was interested in working at GitLab a couple years ago but the salary calculator changed my mind. It lumped all the cities in Oregon together which gave some weird results depending on which city you live in. I can't imagine how wonky the data gets internationally, and it seems like the fairness of your salary would depend on the accuracy and granularity of the data GitLab has for your particular region.
Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by SuperQue on Wednesday September 19, 2018 @05:07PM (#18027714)
Yup, as a hiring manager I lost a couple of good hires due to the comp calculator. Especially in markets, like where I live.

The market for engineer salaries is much higher, due to the demand. But the cost of living is very low, by comparison.

I've been complaining about this for a while, but it's one of those things that we can't just vote on and change the whole company salary structure.

Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by toomuchtodo on Wednesday September 19, 2018 @11:43PM (#18029596)
> but it's one of those things that we can't just vote on and change the whole company salary structure.

I know you alone can’t do anything about this, but the longer this painful task is put off, the more difficult will be to rectify as Gitlab grows (more people = greater labor cost expense increase when the problem is addressed).

It’s peope ops debt.

Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by detaro on Wednesday September 19, 2018 @06:54PM (#18028290)
Just looking at Germany: the salary calculator assumes everything outside a select few cities is costing the same. I sincerely hope they don't use that calculator to make the actual calculations for candidates but spend the effort to calculate an actual number for the location, otherwise that's entire areas that are just laughably inaccurate. E.g. Stuttgart, according to some numbers the city with the second-highest average rent in the country is not in a special case and thus assumed to be in the cheapest class. Let's estimate CoL 30 % higher than Berlin, 10 % less compensation.
Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by mi_lk on Wednesday September 19, 2018 @01:46PM (#18026101)
I really don't find it convincing. If you pay as much as your competitors, why would talents in expensive areas would be discouraged to apply to your company and go to your competitors?

If you're assuming that big city people would feel bad because the small city people get paid more in terms of cost of living, then I'd say that's a bad assumption. People living in any city should know its pros and cons, why is it up to you to decide that the cost of living is the metric?

Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by djloche on Wednesday September 19, 2018 @03:30PM (#18027016)
There's serious room for improvement in the salary calculator, calculator to account for growing metro areas, and I think most of this comes from trying to rely on numbeo for your rent indexes. Eg. Why in the world doesn't Portland OR have its own rent index vs rest of OR? The 'Hot Markets' adjustment should also take a wider account for cities / towns / suburbs that are probably also booming. For example, I'm in the PDX metro area, but on the WA side of the river. My housing costs have gone up 41% to 2.5 years thanks to the booming housing market here, but the current gitlab calculation doesn't account for it thanks to the combined factor of being in the metro area but not in the right city/state, combined with the fact that the big growing metro area doesn't have it's own rent index. Of course, this could be smoothed over and fixed as part of the hiring process, but it would be nice to know up front that you were using up to date data in your attempts to pay market rate salaries.
Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by dx87 on Wednesday September 19, 2018 @01:37PM (#18026014)
So high COLA areas typically already have better schools, utilities, and public services, but you reward employees living in those areas with higher pay because it would be unfair to pay them the same as people in lower COLA areas? Why would anyone choose to work for you if they don't live in a high COLA area?
Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by pritianka on Wednesday September 19, 2018 @01:42PM (#18026065)
That's probably usually true but as an SF resident, I can tell you the schools, utilities, and public services aren't what I would call world class here :p. Wish this was more like New York that way hehe.
Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by ahkurtz on Wednesday September 19, 2018 @03:02PM (#18026803)
Spend some time in the Midwest or deep South.
Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by pritianka on Wednesday September 19, 2018 @05:16PM (#18027791)
Hi folks - appreciate the discussion here. Our ceo put down his thoughts in the GitLab handbook about our policy to pay local rates - https://about.gitlab.com/handbook/people-operations/global-c.... Do check it out. Doesn’t mean the calculator is perfect but speaks to the universal comp vs localized.
Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by 0xffff2 on Wednesday September 19, 2018 @08:59PM (#18028904)
FYI, #2 on that list should say "than" rather than "then".

Also, the link to the compensation calculator is 404 for me.

Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by agensaequivocum on Wednesday September 19, 2018 @04:39PM (#18027505)
And now you are just discouraging those in cheaper cities such as myself.
Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by fierro on Wednesday September 19, 2018 @01:59PM (#18026230)
that's a weak argument; some places cost more to live because they are better places to live. It's a personal decision to live in New York over Kansas
Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by nserrino on Wednesday September 19, 2018 @05:59PM (#18028011)
Ok, so maybe people in high cost of living areas aren't discouraged when the salary scales with their cost of living. But doesn't that effectively bias gitlab against those candidates because they have to pay them more? At some point there are unavoidable incentives that crop up as a result of the asymmetry.
Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by pritianka on Wednesday September 19, 2018 @01:14PM (#18025792)
Re:GitLab raises $100M from Iconiq, GV, and Khosla, at $1.1B... by samueldavid on Wednesday September 19, 2018 @02:16PM (#18026381)
so by his words, it means that if I live in a third world country but I work as hard as my peer in SF I'm going to get paid less by a unit of work? even tho we both are equally good and working as hard?