Ethical behaviour, from my perspective, would be to compensate the employee, regardsless of his legal rights. In a more worker-central system, the worker should have easy recourse to an official judgement for his money.
In the Netherlands there is even a concept of culpability in laws regarding firing. Mess up too much, and the employer will have to pay a premium on the disengagement fee. And while our economy is moving towards a lot more 'sole employee contractors' with less worker-rights, you still have rights and a way to affordably enforce them. For them (only) basic contract law holds. That would probably mean paying the full 3 years in this context. A contract _is_ a contract.
If it had renewal intervals, that means he wasn't legally entitled to 3 years.
This is likely why he wasn't paid for the interim either. The best the company could do would likely be to bump up the future rate or offer a "signing bonus".
Being a contractor is not at all like being an employee despite how similar the responsibilities are. You have to watch contract details like renewals like a hawk. This guy and his recruiter should have included compensation for failing to notify when not renewing.
If you keep showing up to work and your superiors keep managing you (and especially if you keep getting paid) the contract remains valid beyond its stated expiry date.
The worker should not abandon the company during their time of need because of an unfortunate legal SNAFU. The company, in turn, should take it upon themselves to ensure that the worker doesn't suffer economically for having done the right thing by them.
Workers and management on a team ought to be able to trust each other to that degree, even if we understand that the interests of all parties are not fully aligned. That trust goes both ways.
Take that too far, tolerating abuse of trust, and you betray your obligation to yourself. But in small amounts, it's admirable.
Or, if you are saying that they shouldn't stay even for a day, even in the face of an emergency, then I disagree. Even if they don't have a legal obligation to do so, I respect those who would, like this worker. And I would prefer to work along such people as colleagues, trusting that if they could help it, they wouldn't leave their team in the lurch.
I don't like the idea that complete lack of trust and hairtrigger hostility should be the default mode of workforce participation.
As advice to a worker in this situation, it certainly makes sense to gut it out and take the risk of doing work without pay. It's, for most people, probably a much smaller risk than risking getting "really" fired without first having another job lined up.
Then complain to the employers, who are the ones who created that culture.
For what it's worth, I attribute the worst amoral behavior to corporate personhood rather than capitalism. Thus my preferred remedy is to eliminate corporate personhood, rather than capitalism.
I would agree with your point of professional contracting: contract for the worst and write out scenarios in contracts.
In this case though the employer acted in a way that signalled renewal and the contractor delivered in good faith. Back to contract law and ethics: are services delivered possibly without contract but in good faith without value and compensation?
The Netherlands sounds a bit employer friendly in the UK mess up at all in firing some one you automatically lose even if the employee is as guilty as sin and was caught bang to rights
Sounds very strange that he wouldn't care to do a bit of paperwork, which he from the sounds of it could probably well justify to do on company time, with the manager and director being supportive. Or get the agency to do it for him, and bill them for the trouble. Or whatever. Something smells a bit fishy about that part of the story.
And if there's anything in the comments about "the manager and director being supportive", I don't see it -- where did you get that?
As for "fishy", I find it very strange that someone writes an article emphasising twice that they're out three weeks of pay, but then couldn't be bothered to do anything about it. There's breach of contract, this isn't a long and arduous appeals process, it's open and shut, and if it isn't you have a lawyer deal with it, and recoup expenses, too. And if the guy just doesn't care about it, then why does he mention it twice?
And for the purposes of this, and the other sub-thread that is incredulous about this, this is not an American thing: If you're a contractor in Europe, and you don't get paid, and you then don't do anything about that, then you don't get paid. There's no process that automatically fixes things when the aggrieved party doesn't ask for them to be fixed (and yes, even in Europe, there's a bit of annoying process and paperwork to deal with).
Even if he's legally entitled to the money, bringing a lawyer into the mix is likely to sour his relationship with his client (he's a contractor), and—rightly or wrongly—could give him a bad reputation in the local community, making it harder to find work in the future.
I'd actually rather people sue over this to establish some kind of case law where companies' legal teams tell their management to make a default policy of giving the missed pay on demand. There might already be case law on it.
I suspect this is the difference. If this company is incapable of not firing someone, I imagine their appeals process could be equally miserable. Sure, maybe the manager and director want to repay him, but actually releasing funds to pay someone who "wasn't employed" is going involve a lengthy battle with some HR/Accounting computer system that just wants its invariants not to vary. Depending on somebody's financial position, I can see them deciding to just walk away on even a large chunk of money to avoid the mess.
But, of course, the author is perfectly within his rights to just not pursue this, and I have no idea what processes he'd been told to expect for this -- it's just strange that he would emphasise something he doesn't care about in the post.
This is a good point. I was thinking that no matter how trivial the money, actually dragging a check out of the accounting system would be a serious hurdle. But the solution I missed would be to sic legal on it - their machine tends to beat out everyone else's.
“Made available? I eventually had to go down to the cellar to find them.”
“That’s the appeals department.”
“With a flashlight.”
“Ah, well, the lights had probably gone.”
“So had the stairs.”
“But look, you found the forms, didn’t you?”
“Yes, yes I did. They were made available in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying ‘Beware of the Leopard.'”
Now we're not just talking about a lost opportunity to reward a loyal worker. If you're right, somebody ought to be going to jail.
(1) "Small" in relation to the whole contract deal; what's one employee's salary in a million-dollar agreement between two corporations?
Real story from one of the (big) french telecom companies I worked for, as a contractor (a few years ago)...
In that company, a regular employee was given a full desk, contractors were only given 2/3 of a desk (meaning 2 desks put side by side for 3 persons).
Also, contractors were NOT allowed to go to ANY conference. Even when it was about technical stuff that was directly for their project. We had to rely 100% on a transmission of information by our managers/team leads. This led to humorous results, to say the least. Things like: a BIG meeting with plenty of people and managers, who then decided a HUGE technical change on the network, without the ONLY expert because he happened to be a contractor. Once given the results of the meeting, the guy was in a "WTF?" shock. He told me that be immediately binned the request: it basically asked him to disable the authentication server! Not the best decision for a BIG ISP, LOL. Seriously, that's almost beyond belief. (But I have other incredible stories similar to this one).
As a contractor, I have really been mistreated A LOT. So much so that I've sworn never to do it again.
If contractors are the only expert in a domain, there are big problems. Of course in corporations this is quite frequent - middle managers have yearly budgets for contractors, but aren't allowed to use that money to increase their headcount.
A company I work for decided to get a contractor in to run a £40m project. This makes sense for a management perspective, they get to blame the contractor (who's already left) if it fails, and they get to claim the glory if it works. It's terrible for a company though.
If I want 500 cables run in a data centre, or even 5 cables if it's a long way, I'll get a contractor in. Saves me a day by not having to do that work neatly and lets me do more important things (like ranting on HN). If I want someone to build me a fancy gui, I'll specify the frameworks, and let them mess around with the look and feel, but ultimately I own the output of the work, I need to be able to deal with it as if I wrote it myself.
>Some of that work included renewing my contract in the new system... When my contract expired, the machine took over and fired me.
As I interpreted the piece, it was a three year contract which was stored in an old system, and not transferred when that system was replaced. So the firing was triggered by the system no longer seeing any valid contract.
If that's true, it would be breach of contract. But if it was a rolling contract expected to end after three years, then yes, it would be a weird situation but not a breach.
There are exceptions, but they are pretty rare in tech.
So the contract was negotiated at a specific price point for (say) three years but every X months the other party can opt out by not renewing. They only commit for a certain term.
From what I understand, you can only sue for $1000 or less in small claims court. An IT contractor who is making $1000 or less per week has bigger problems.
[1] https://www.nolo.com/legal-encyclopedia/small-claims-suits-h...
Of course you'd shop around for the Bailiff company with the worse reputation and get them to send the lads who moonlight at that dodgy night club as Bouncers.
This sort of thinking kind of makes sense in a world where almost every company is a big factory company with their workers primarily doing repetitive physical labor. And the business management world has not adapted at all to the transition to mental labor. Their businesses fail and suffer for this, but as it's a universal condition (yes even among Google and such... if the company has a physical office, then they haven't even done the obvious to benefit from the move to mental work) there's not much pressure motivating change.
I billed 40 hours a week the entire time.
IMO because the generally demonstrated position of the labor force is that companies do not have to (which I hate, to be clear).
IMO, employees buy into the employer/owner-propogated myth that they are "lucky to be employed." As a result, employees greatly undervalue their labor and give up any leverage to make employers do the right thing.
Having been around the block a few times, I view 'work' as a transaction in which my employer and I need to realize fairly mutual benefits: most people don't. Employees generally see jobs and titles as a way to assess their societal value. And employers, knowing that, can do pretty much anything they want to people, dangling the occasional carrot to encourage higher worker output, but mostly working w/sticks.
This is also contributes to the zero real wage growth in a supposedly tight job market.
TLDR: power dynamics and poor 'game play' on the part of employees
Why has this company not made their loyal worker whole? He stayed there when they needed him even when their system was trying to lock him out.
They need to fix this. If they don't, they are not a company anyone should work for. Perhaps the worker did not want to risk making a big stink, but a manager should have taken the initiative. Humans were involved by the end and well aware of what was going on.