That's kind of the exception that proves the rule, you think?
That is, your outlining of the situation gives a strong suggestion that this sort of thing is common and unless the contractor has pull (say, a relative that works at Google), they can't do anything.
a) the rule is a heuristic, not a hard-and-fast rule, and
b) the notability of exceptions suggests that the heuristic is pretty good.
In other words, if the exception is, in fact, exceptional, it reinforces that the heuristic is reasonably valid for non-exceptional cases.
In this case, the fact that it took the intervention of the family-friend-who-works-at-Google-HQ to resolve a pay dispute is an exceptional circumstance, and reinforces that for most people, because presumably most people don't have a family friend who works at Google HQ, there is no recourse to pay disputes.
Hence, the exception—by being exceptional—proves the heuristic rule that most employees of these contractor corps have little power to negotiate for their rights.
The German cognate would be "prüfen", the Swedish probably "pröva".
So, the exception tests the rule.
[1] And the standard is, of course, a reference exemplar of some sort.
You have no proof that it was exceptional. All you have is one case. You have no idea what other people in pay disputes end up doing.
> You have no idea what other people in pay disputes end up doing.
But also this is a super weak argument. I don’t have “no idea”—I have an educated guess that most people don’t have family friends who work at Google. Most people don’t have the resources to sue an employer over a few hours of unpaid labor. Wage theft is one of the most extensive unprosecuted crimes, that’s been studied and shown many times.
Are you suggesting that one should assume that most low-level employees in pay disputes get happy outcomes? That seems…naive.
Metaphorically.
I mean, while we're being pedantic we may as well get it right.
Or to go with synonyms. Solicits the question. Entreats the question. These are the literal meanings of the words, and they work fine.
I always wondered about that word. If you want to test yeast, you just put it in some sugar water & see if it foams.
But then, I guess you can't do that if it's mixed with flour & other stuff?
It still retains that archaic meaning in the phrase you mentioned and terms like "proving grounds".
Edit:
And like so many other proverbs like "A few bad apples", "Blood is thicker than water", "Carpe diem", "The exception proves the rule" means exactly the opposite of what most people think it does.
I’m bringing this up because, for many years, I was one of the folk who spread the idea that it actually was supposed to mean “the blood of the covenant is thicker than the water of the womb.” But there’s no strong historical basis for this, lovely as the idea may be.
—
As for the “bad apple” one, I didn’t realize that it was commonly misunderstood. I always felt like someone mentioning that someone was “a bad apple” was an almost violent accusation: the person needed to be extricated from the group, less the group become infected by their corruption. I am now trying to think back to times when I’ve heard this one used and wondering if I misunderstood the intent.
Yes but "There is little evidence of the phrase being used in this second way.", citations located at wikipedia.
So I think it makes more sense to go with the interpretation of "if someone lists an exception, then that's proof of a more general rule that it's an exception from". But with that use, something specifically has to be an exception. Anyone applying "exception proves the rule" to an anecdote is using it wrong.
It means that if someone bothers to write an exception in a law, say e.g. "but in case window is broken by stone smaller than 1 cm in diameter, then it's the owner of the window that should pay reparations", then in the general case it's likely the thrower of the stone that pays, otherwise there would have been no point in adding so specific an exception.
When you see text "kids under age of 3 years don't have to pay", you can conclude that older people are supposed to pay.
The analogy for Google situation would be if hypothetically someone found an internal e-mail written by the boss of Google HR department saying "contractors who have relatives in Google, or who have published their story on Hacker News front page, need to be fully paid for their work". Then we could conclude that other contractors typically don't get fully paid, even if there is nothing in the e-mail saying that.
I disagree with most of the commenters that want to apply the phrase to heuristic claims.
Some how it's morphed to colloquially mean "yes, that one exception aside, I'm right and you're wrong" as if the negative somehow reinforces the positive..
The phrase "the proof of the pudding is in the eating" helps understand this. The pudding may prove to be bad or good. Find which proof by eating it.
Logically the statement says nothing beyond what it says, but implicitly by providing the exception you’re stating that the general rule is different.
It’s a perfectly rational linguistic argument, though often misused outside of that context.
The argument is that not being able to reject the null hypothesis means that the null hypothesis is correct. This is an invalid argument. We're sorry but we can not accept your submission at this time.
These outside companies had minimal oversight from Google, by design.
Could this be so that the google corporate toadies could bid out the lowest possible price, yet remain isolated from the predictably unethical, shoddy, or even illegal practices of the cut-throat priced contracting companies?It just seems strange that you’re lauding google HR, when your description suggests google was complicit, if not directly responsible, for the whole setup.
https://www.lesswrong.com/posts/9fB4gvoooNYa4t56S/power-buys...
The fact that a cottage industry of less than law abiding contracting agencies provide services to Google is more an issue of CA's employee protection laws than Google's responsibility.
Consider the current/default rate of wage theft via salary employees not paid for overtime despite being eligible; it's rampant in the SE industry because it's logistically easier to pay someone 10% more than to keep track of occasional overtime.
Therefore whenever a large company contracts something out to a smaller company, you should immediate expect more shady practices. My point is that Google's only role in this case is making something unknown... known - plenty of small shops unrelated to FAANGs break the same rules.
.. and yet, it happened. I was there. Maybe you should look up "slave labor and clothing factories" or "janitorial service companies."
A modern company that contracts with another company to do something for them does not get to completely wash its hands of their practices. Up to a point, they do, but when the contractor egregiously violates the law, then they usually get involved anyway. Judges and juries and regulatory officials and employees take a very dim view of illegal conduct by your contractors. It reflects badly on you.
In this case, I don't know what happened afterwards, but I would guess that Google amended its contracts with those companies to better regulate cases like this. Just a guess.
Maybe they even intervened without mentioning my cousin's name -- maybe they just said "hey, in general, you can't violate labor laws, and you definitely can't refuse to pay people for being too slow!"
They do if they want to maintain their position that the employees of the contracting firm are not their own employees.
If an employee is not getting paid by an employer, that is between the employee, the employer, and the state department of labor.
Slave labor and clothing factories are not relevant in this case as those operate in other countries where the government's labor laws and enforcement are much less effective than the US.
Janitorial service companies is what I am referring to. If my company hires a janitorial service company for $x to perform janitorial tasks, then the janitors are clearly not my company's employees. But if my company now starts getting involved in compensation disputes between the janitorial service company and its janitor employees, now my company is risking wading into a dispute in which it has no need to and risks raising questions about whose employees the janitors really are.
Perhaps what you said really did happen, but I cannot find the motivation for people in Google's HR department to do so, especially if it was in a state like California with a pretty decent labor department that would undoubtedly support workers who did not get paid for time worked.
In NL you can forget about that. It use to be that you could stick some "fictional" company between you and your employees and get out of jail free for everything, including salaries. Jobs 1-4 hours per week made it extra unlikely for any employee to run the extra mile after they were left without a name, address or phone number after about 3 months. Taking the bankrupt company to court was expensive and unlikely to work. People don't take a 2 hour job unless they need the money.
Now the obligation to pay salaries applies all the way up the food chain.
The way contracting usually work is that the contractor must submit timesheets daily or weekly to a supervisor at the parent company. The supervisor must approve the timesheet. The contractor will be paid the hours in the timesheet.
The story is a classic example where the manager (google employees) refused to acknowledge the hours for no valid reasons, preventing contractors from being paid.
Gotta escalate to HR to get paid and fill formal complaints against the bad manager.
When there's a problem with the employee not being paid, the root cause often goes back to the employer blocking the pay in the first place.
However, it turns out that "arms' length" doesn't mean the contractor can get away with absolutely anything.
Contractors cannot be at arms length. There has to be an arrangement with the employer (Google here) and the contracting firms to pay. That means there has to be a timesheet for each employee. Could be filled by either party.
You said your cousin wasn't paid because somebody (implying from Google Search) said she took too long and refused to pay her. To me that sounds like a normal story where Google had to approve the hours/pay and they didn't. The excuse from Google employees that they are detached is fishy at best, they wouldn't be able to prevent payment if they were.
... as if it's better if they aren't involved? We are commenting on a story about that... seems like if they knew better, they would actually get involved to makes sure that this don't get out. The bare minimum is to pay the ones that complains, that way you at least minimize the risk of this getting out.
On the actual jobs you get so many timed tasks that a single one wouldn't even stand out, really.
No. They had an entrance exam, and my cousin had passed it and signed on.
2. Aren't Contractor like these fairly normal in Silicon Valley. Apple are the same as well. Even worst most contractor were told there is a chance of working inside Apple if your job was good enough.
3. Very rare HR does the right thing.
https://arstechnica.com/features/2017/04/the-secret-lives-of...
Those "raters" were contractors to the independent companies, and had no Google privileges at all. They couldn't come to campus and eat at the cafes, for example. They had no direct contact with any Google employees. I helped a relative get hired as one of those. This was about 11 years ago.
These outside companies had minimal oversight from Google, by design. My cousin joined the Search rater company and was given a test problem, which was timed and they had max times allowed. When she finished, they said "sorry, you took too long, we're not paying you."
I raised a stink and HR sent a representative to meet with the Search people. I sat in. The Search people were obnoxious little corporate toadies who claimed they couldn't interfere with any particular contractor's case, because of the legal separation requirements.
I so enjoyed watching the HR rep calmly and politely tell them, "That's great! Good job, you guys! But you know... when you hire someone and they don't do a good job, your remedy is to fire them. Not to refuse to pay."
She got paid.
I can't make any general statements about what happens to everyone, but in this particular case, I can't complain at all about HR's handling.