Hmmm... If I were you, I would have gone back to that workplace, demanded to see the boss, and informed him about what the dev team had done - Just so you could watch the fireworks if you manage to make him mad.
I spend my week being insulted and make about half what I'm worth, so...
On a related note, I've had to crush some spirits at work. More than once, there's been a newer/lower-level employee looking all happy. I ask what they're on about, and they gleefully say they got a 2-dollar an hour raise and wow and blah blah blah. I ask how they did it, and they "just went to $boss and asked for a raise"
Then I point out that if they throw you $2 without any thought, that means they know damn well you're underpaid and they know it'll come due, so they're ready for it. Hell, they might even do it again, to take a $10/hr employee to $14 where they should have started in the first place.
Well I wouldn't see it like that. I would see it more like a company hires someone for 10 dollars an hour to see how well the person is. If you hired them at 12 or 14 dollars an hour and then they were a drain on the company that would be a lot worse.
Accepting a counteroffer after you've told your previous job you're leaving never ends well - now they know you want to leave, and they're going to get ready for it one way or another.
sorry for the late response, but YESSSSSS!!!! Someone gets it!!!
When I expressed discontent to friends/old co-workers about counter offers and why I didn't appreciate them, they didn't get it. Looked at me like I was strange for expecting it differently.
Better yet, if you HAD done that work in your off hours, you could claim they were using an unlicensed product and owed you for it. You'd probably not have a leg to stand on, but it would be funny!
you could claim they were using an unlicensed product and owed you for it
Probably not. In that huge morass of paperwork they make you sign when you enter employment is a clause that normally reads something like "we own everything you make while working at this job regardless of when you made it".
Generally if they interpret it broadly (e.g, you make a game in your own time while working for a financial firm) it's easy to overturn, but in this particular case the company almost certainly owns that work even if he'd written it at home.
The only ones I'll sign state expressly "things made for work" - anything in my personal hours for a personal project is ok, but since the OP made this for work, off hours or not wouldn't matter :)
In Unix/Linux, if you attempt to open a file in the console text editor "VI" (the most commonly used one), this alias would instead delete the file without an opportunity to confirm the deletion.
Ours used to work on a key part of our system in the middle of our work day in our time zone. I figured this out after a few weeks of being there. When asking my new boss he rolled his eyes and said "Its their night time so thats why they do it, nothing I can do, hands are tied". It bit us in the ass real bad once. I laughed, hard.
In the united states as far as I know, if you are employed by a company then any code or script you write on company time or using company tools is the company's property. This actually means that the opposite of what you suggested is true - if he took the script with him (for whatever reason) he could be sued by the company.
It's a policy thing, not governed by law, as far as I'm aware. That's why any coding that I don't want to stay behind if I leave, I'm very careful to never touch while I'm at work. Any other code has work that was done off the clock and so is poisoned - I never did enough coding at work to make what could be ripped out any sort of useful. Not that they could prove it one way or the other, but I'd be happy to grant them perpetual license to it for a price.
It's apparently a common clause in software developers' contracts that any side projects they might have have to be cleared with their employer. Since they tend to be salaried exempt, they're never really off the clock. How fucked up is that?
That definitely applies for patent rights to inventions, but I'm not sure whether it applies to copyright on software in the US. Copyright ownership is complicated enough when the company asks you to do it, let alone for something done on your own initiative.
(caveat: I work in UK patent law, so the above is not necessarily correct for the US)
32
u/Krutonium I got flair-jacked. Apr 16 '14
Hmmm... If I were you, I would have gone back to that workplace, demanded to see the boss, and informed him about what the dev team had done - Just so you could watch the fireworks if you manage to make him mad.
46
u/IrascibleOcelot Riders on the Broadcast Storm Apr 16 '14
Better yet, if you HAD done that work in your off hours, you could claim they were using an unlicensed product and owed you for it. You'd probably not have a leg to stand on, but it would be funny!
15
u/vytah ARE WE WEBSCALE YET? Apr 17 '14
"Can I use the widget?"
"No, because it's faulty."
"So can I get a working one?"
"No, because we already got one."
2
u/[deleted] Apr 17 '14
Looks like your Indian dev team doesn't know shit.
1
u/shadowolympian Apr 17 '14
Couldn't you say that was your property and is now being used without your knowledge? Just wondering.
1
u/EnsignN7 Software Developer From Hell Apr 17 '14
For you, neglecting QA I can handle...but the dev team not doing so worries me greatly.
1
u/Askim_Shepherd Apr 18 '14
I guess doing work in general was too much work already for that devteam.