So much misinformation in this thread. H1B's don't get paid lower. Law requires that they be paid market wage and no native workers are being undercut.
If you see this happening, then you can actually report it to DoL (I have had a call from a DoL investigator about H1B abuse at a past employer based on a complaint filed by an employee).
The law also says there can be no gender wage gap.
I've worked at several big tech companies and they all abused H1B's. The immigrant workers were paid a lot less than citizens. It pissed me off because the immigrant workers were treated like crap and also I would imagine it puts downward pressure on my own salary.
I worked at a company that gave referral bonuses to employees for new hires. It went like this: $2,000 for a white. $3,000 for a black or Asian. $5,000 for an Indian. HMMM.
There's little incentive for an individual to report anything. You've seen how "whistleblowers" get treated. Up against a big company with a legal department, chances are good that they know how to put up chaff, redirect, deny and obfuscate their abusive practices. Why stick your neck out when it's a systemic problem?
I upvoted you because you bring up a popular myth.
So you are correct that they have to be paid market wage. But the details matter here. For the DOL, the "market wage" is the "prevailing wage". This is a function of the job classification (title), wage level, location and (most important) which wage survey they choose to use.
By now you can probably guess how a company that wants to underpay can use these levers - under classifying, moving them to a suburb with less employers for that job, using a different wage survey etc.
You could look for any job. If you have a skillset some employer really wants, they will think about it if you let them know that you'd be interested in working for them, remote. Of course you risk running into a company that isn't very remote friendly (and the experience can be painful e.g. due to poor communication), but it's surprising how many companies that don't really advertise themselves as remote companies have or have had remote employees.
I have landed my previous and current job, both remote, via Stack Overflow Careers. On the first one I was approached by a recruiter, for the second I have applied myself after narrowing down some search results.
I loved doing OR for my final project at Uni, it was great solving the travelling salesman problem for a taxi network routing it to the correct people and picking people up in realtime around an imaginary map of points. I remember thinking as I took a cab into halls from the station "wouldn't this be amazing if I could have a device that told me exactly where each cab was at any point and maybe hook into the satnav somehow". In 1999 [1].
Do you have any suggestions for people who want to self-study in OR? I would like to know more in general but am specifically interested in applications to healthcare
My recent previous employment was in healthcare (on the insurance side) so I can give you some relevant insight
I do want to mention that on top of any self-studying, try to attend a talk or two or start following some feeds online that are close to actual healthcare operations. Operational teams are the ones who have to figure out what to do even when there is no good answer. the easiest way to keep up with which topics are most valuable right now is inside knowledge.
There is no purity in the OR field outside of phd's doing their research - it is entirely about getting shit done efficiently, however possible, to the extent that the operations team can understand. That last part of that sentence is a big catch. For example, if your 'solution' has interns making judgement calls on data entry (because moving the work upstream is efficient!), you are fucked if you assume that data will be accurate.
BUT there's obviously plenty of skillset stuff you can learn to help you in a general way so here are some important areas:
1: Linear & Nonlinear programming (tool: AMPL)
2: Markov Chains (good knowledge)
3: Statistics & probability (necessary knowledge)
4: Simulation (start with monte-carlo [it is easy and you will be surprised it has a name])
5: databases: SQL / JSON / NoSQL
6: data structures and algorithms (big O notation / complexity)
OR work in general overlaps a lot with business analysis. The core stuff they teach you in school is listed above.
Healthcare right now has a big focus on Natural Language Processing, and applying Standardized Codes to medical charts - and then working with those codes. The most common coding standard in US is ICD-10 I believe.
Other than that it is mostly solved logistical items like inventory control systems that need a qualified operator. You do not want your hospital running out of syringes. You do not want your supplier to be unable to fulfill your order of syringes because you need too many at once. You do not want to go over budget on syringes because there's a hundred other items that need to be managed as well.
Now the important thing to keep in mind is that almost all operations problems at existing companies/facilities have solved their problems to SOME extent since if they didnt then their operations teams would have fallen apart and failed. So in practice it is rare that you are going to implement some system from scratch, or create some big model. Youre probably going to work with a random assortment of tools and mix data together between them on a day to day basis to keep track of when you need to notify people of things. With a lot of moving parts, you will have to task yourself with finding improvements and justifying them. Expenses are very likely to be higher than optimal, and you can earn extra value for yourself by finding incremental improvements.
No one is going to say: "work up a statistical model for me". They are just going to be doing something inefficiently with no idea how to do it better, and you are going to have to prove to some extent why doing it another way will be better - and also be worth the cost of training people to do it a new way. It will be monumentally difficult to convince anyone to make any sort of major change unless the operations team is redlining, so your best skill will be in being resourceful and adapting to the way things are no matter and improving THAT mess - not creating a new way of doing things.
Databases house the data you need to make your case. SQL was the norm, but a lot of stuff is JSON now. You might need to work with an API, add django to the req list.
Simulations let you test multiple scenarios of resource allocation on a complex system with moving parts (for example, resources includes # of hospital rooms as well as employees and their work schedules). Statistical analysis lets you verify the output of your simulations as meaningful or not. There are proprietary simulation programs that do the A-Z of this for you if you know how to configure it (ARENA), and theres pysim + numpy + pandas + ...
Markov chains are related to building a model for your system. It's theory stuff, but helps wire your brain for it. Laplace transforms are "relevant" somewhere in this category
(non)linear programming is the calculator of the fields distribution problems. In practice you create 2 files: a model file and a data file. Model file expects the data file to be a certain format, and is a programming language for processing the dataset.
For example, if you manufacture doors and windows at 3 locations, and sell them at 10 other locations, and you have a budget of $10000: how much wood and glass do you buy for each manufacturing location and how many doors and windows do you make and ship to each selling spot from each factory? The answer depends on data - price each sells at, cost for each plant to produce, capacity of each plant to produce, cost of transporting from factory to selling location, etc. So you make a model file for your problem and then you put all the numbers in a data file. You can change a number, run the model again, see if the result changed. You can script this to test many different possible changes
Data structures and algorithms:
There are a lot of different optimization algorithms, all with different use-cases and theres no real upper limit on learning them; so this area can be a good time sink... since someone else will have already coded the implementation but you are providing value in knowing how to use it. Therefor - you dont need to learn how to make the algorithms or what magic they perform outside of whatever helps you understand what its good at. Outside of research, its unlikely this stuff will really get you anything other than maybe being able to impress at an interview - BUT who knows, maybe you find a use-case for some random alg that is career-defining.
I know a ranted a bit, and I didnt proof read, but I hope there was some helpful info in there
What would you call 9 people in a group of ten voting to take away the tenth guy’s stuff because they wanted to? I call it what it is - stealing. Greed. Envy. Interestingly, it will probably lead to more equality; it just won’t be what you’re expecting and I don’t think you’ll like the result. At this point though, the people probably deserve to get what they want and get it good and hard.
Small thought experiment: Imagine an agricultural society where the nobility own the land, and serfs work it for subsistence wages only. The nobility largely don't work, and live lavish lifestyles supported by others. Nothing too unusual historically. In those circumstances, is maintaining the status quo the only morally correct choice, and any deviation from that "stealing?"
I don't think it's reasonable to measure a society's morality by its tax rates only or to draw an equivalence between taxes and theft.
It's true that minimal government and taxes worked well in the US's early history. But if you think about it, that was an agricultural society where the main source of capital, land, was practically free. It's not surprising that relatively pure capitalism worked OK then, but historically it seems to have worked out less well in almost all other circumstances.
These days a lot of capital is in stocks in global corporations, with barriers to entry measured in the billions of dollars. It's not as simple as moving to the frontier and finding your own plot of land.
I think an ideal society delivers broad-based prosperity and individual freedoms with a dynamic market economy. And tax policy should preserve incentives to work and invest efficiently. But if there is a conflict between broad-based prosperity and zero tax rates / income redistribution, like in the example society above, the former should definitely be chosen over the latter.
I think going the other way around, rather than leading to a capitalist paradise, will only lead to the rise of ideologies that advocate heavy-handed state control of the economy, probably to the detriment of everyone.
You are wrong on that. A company I worked for was investigated after a complain about H1B process. I actually had an investigator call me asking all kinds of questions. They do take complaints about H1B abuse seriously.
