Radiation exposure is well understand and extrapolated, and has been for years.
The public risk perception of radiation is so far from reality, it could possibly make us do stupid things.
Your perception of the risk from radiation is so far from reality, you've simplified the model to the point of being useless.
That's been my experience of your posts, that all of the knowledge gathered since the 1950s just doesn't exist. You don't understand:
The difference between a radionuclide and the radiation it emits
The difference between internal and external radiation exposure
The difference between being exposed to radiation and having an emitter inside you exposing you 24x7
What bioaccumulation is
That detection in food and water is really hard
That you can eat a radionuclide
That you can drink a radionuclide
That you can breathe in a radionuclide
That some radionuclides appear like different types of micro-nutirents to a matabolism
That it deposits in different parts of the body
That it can be organically bound in the body and not excreted
That organically bound exposure increases absorption of radiation
That it can be chemically toxic
That children are more susceptible than adults
That an effect could be death
That an effect could be cancer
That an effect could be gene damage
That an effect could be failed birth
That an effect could be a birth defect
That an effect could be transgenic disease that effect the next generation
That an effect could be reduced brainweight of, and lower IQ in infants
That there is still stuff we don't know
Then you:
Ignore facts even when they are cited from reputable sources
Don't seem to want to understand
Continue to shill as if you have an agenda
Claim everything is FUD
Minimize the apparent harm
Ignore data collected from unbiased sources
Refuse to accept that some data *is* biased Nuclear PR
Refuse to accept the impact of media blackout for Fukushima
Refuse to accept the work of Ukrainian scientists studying Chernobyl
There is a reason the NRC uses ALARA, figuring out this stuff is complicated and the easiest thing to do so your brain doesn't explode from thinking about it is to keep the potential risk of exposure ultra conservative.
Wow, you are one stupid motherfucker. When 12 different people write a page of a book, who owns the copyright on the page? Later dumbfuck. Better yet, stop wasting my time proving how stupid you are; I get it.
It's ok, we're done here. You have nothing useful to contribute and I'm tired of you trolling me. Sounds like you're having a bad day.
Sure... they'll either offer you less, as you're not given them all that they want, or they'll simply get someone else.
Not when I explain to the project manager how I will meet or exceed their schedule variance and reduce the amount of risks and issues in their project control book. My instinct tells me what buttons to push.
A lot of the time you're not dealing directly with the clients, you get the deal with one of their "preferred vendors" *, who won't/can't negotiate with the terms of the contract, as they have existing contracts with the client.
Different horses for different courses. As always, YMMV.
Is owning the IP to code you write for someone else really important to you?
Not all the time, some code I don't care about. However some code is hyper useful and represents a paradigm shift in my thinking that I use to accelerate other things. Sometimes the ideas are more valuable than the code because I'm going to translate that idea to another language.
So with one stroke of the pen, whilst I read the contract, it is gone and the onus is on them to agree
That's not how contract law works. Unless they initial the change, the presumption will be that they didn't read your alteration, and therefore it isn't binding.
Maybe where you are. I initial the change, I am a signatory to the contract. For them to accept the terms as is, they sign on the dotted line and it becomes binding. I keep a copy and so do they.
Remember, they'll have real lawyers.
So do I.
That being said, they may well agree to the change, especially if you word it such that you'll be using open source code in places, and such code including changes will remain public. Some very big contractors use exactly this approach (and then don't share their changes with the larger community, but that's a different issue).
That's interesting but it sounds like they're violating the GPL when negotiating to maintain copies of my source code that I write and am interested in keeping means we all stay friends and everyone gets what they want. I'm not interested in taking what I haven't written and sometimes I'm not interested in taking what I have written. However taking what is useful to me means they get much more in return.
If you are a contractor then they don't own your code. Even as an employee you still own the moral right to your code.
The most common situation is that you wrote the code as a "work for hire", either as an employee,
In that case, everything you do, even at home, is theirs. If they want to fuck with you and you build something cool and put it out there, they can come after you and claim that what you created is theirs because that is what you have agreed to. You work for them, not for you.
You had better understand what you are signing, it one thing to give your code away, I don't think you would feel the same about having it taken.
or if as a contractor you explicitly assigned the copyrights exclusively to the employer/client.
Well, if you've done that, you have no claim to your IP other than Moral rights of attribution.
I don't know what country the OP is from, but speaking to those in the USA, could you provide some explanations (and legal citations to support them) about "moral rights" and how this would allow you to give that code to someone else such as a potential new employer?
Local legislations vary, which is why I say you have to take personal responsibility for knowing the law where *you* are. If he under a NDA, nothing. If he has assigned copyright, nothing. He could argue fair use to assert his moral rights of attribution to show code he created, however YMMV depending where you live. Failing that his moral rights are 'yes he worked on that project'.
You just confirmed what I said is true and then tried to set up a strawman to make it sound like I said you specifically don't own the rights.
I did no such thing to confirm your ignorance. You skipped over the part where I challenged you: I employ a lawyer to ensure I meet my legal obligations... What do you do?, the obvious answer is, nothing.
There is no jurisdiction in the US where the legal situation defaults to "contractor owns the code".
The US is a signatory to the Berne convention. As programmers I think your country has specifically given up some of the rights you had to the MPAA simply because you did not defend your rights. I don't specifically know what your situation is wrt local laws because as I said: I am saying what is legal for me, where I am. You have to take responsibility for yourself.
Seems like you didn't and the truth hurts you so much you're willing to falsify your own reality so you maintain ignorance about what you have lost evidenced by the contempt you are projecting onto me.
Everything you wrote is a ridiculous babble of bullshit representing an attempt to take the focus away from the fact that you made a completely false statement, and gave people shit advice, in fact. Just admit that you spouted off your mouth with inaccurate information, and that you claim to be super smart, but actually aren't,
I don't see where I made a claim to be super smart, only that I've retained a lawyer and reseached enough about copyright law to protect my rights. I write and record music, I had to learn. When I did I found it applied to the software I wrote. Instead of decending into responding to your emotive outburst and abusing you, let's re-visit the comments I made that everyone seems to have a problem with:
If you are a contractor then they don't own your code. Even as an employee you still own the moral right to your code.
Specifically, if you are a contractor then you own the copyright to your code unless you agree to contractual terms to give up those rights. Anyone with sufficient deductive reasoning should be able extrapolate their legal situation to a corporate entity that has exactly the same set of rights that you do. The difference is they are negotiating from a position of strength so that you will relinquish your rights. But let's not let logic get in the way of me demolishing this "argument" with the relevant facts.
First, Article 10 of The TRIPS Agreement contains an interpretive provision stating that computer programs, whether in source or object code, shall be protected as "Literary Works" by the Berne Convention. Article 4 of the 1996 WIPO Copyright Treaty (WCT) includes a clarification in very similar terms.
Article 6 and Article 7 of the WCT document determine the framework for negotiation. You give up your rights according to WCT 6(2), I maintain my rights according to WCT 6(1) and WCT 7(1,3).
Therfore source and object code are protected as 'Literary Works' under Article 2 of the Berne Convention as original works and nothing in that treaty applies to you submitting your source code to a larger tree negates that right unless you specifically give it up. Specifically Berne Article 2(1,3,5), limited by local legislation which is why I say you need to take personal responsibility for knowing your local laws.
Second, as to Moral Rights, this is the specific position of the OP covered in
> If you are a contractor then they don't own your code.
Jesus, what? Contractors don't own their own code, you're really badly misinformed.
Your post makes not sense.
I get it that people are afraid to stand up for their own rights and haven't learned how to do that, however for you to make a joke about it makes you come off as a coward, Courageous. Is that what you are telling me?. Do you think I'm going to laugh with you and say 'Gee, shucks, I guess I should give up my rights the same way you do and disappear into the banal'. Perhaps I just don't understand the desire for subservience in place of respect.
I see a lot of people here arguing to make their position weaker with employers because they are too mentally lazy to take personal responsibility for their own education in the copyright law that affects them. I've no doubt these people are also complaining about H1B visas as well. Obviously they're not the rock stars they thought they were.
By all means stay where you are comfortable, and complain that no-one stood up for your rights so you can feel that satisfaction of being like everyone else. Don't worry, someone else will take your share and you will give it up without complaint because you don't deserve it. Frankly, it's a pathetic sign of mediocrity to be criticized by sheep for not being a sheep and I'm so happy not to have been stained by it.
If the horror of me sharing how I stand up for my rights is too much for you, then the thought of how I am going to apply Software Patents will be stuff of nightmares for a long time. Whilst you struggle to figure out how to use your rights, I'll be working on extending them. This thread has been unexpectedly educational, I'm certain I won't be the only one using this knowledge to derive maximum strategic value from it in their next contract negotiations.
It is not true that they don't own the code if you are a contractor unless you have that in writing.
Really? So you know all regions, all legal jurisdictions? I am saying what is legal for me, where I am. You have to take responsibility for yourself. I employ a lawyer to ensure I meet my legal obligations and make sure I'm educated enough to negotiate. She has a safe with year on year copies of my codebase all they way up to my local statute of limitations. What do you do?
Some people think it is not moral to violate the law, so if anyone follows your advice they will be doing something that is possibly unlawful and certainly morally ambiguous at best.
You accuse me of moral ambiguity yet you demonstrate no clear understanding of the legal premise behind 'Moral Rights'. Anyone who takes personal responsibility for understanding what their rights are and then uses them is doing what a capitalist society encourages us to do, indeed, what it is there for. My morality is making sure I do what is legal.
My code is a business. I reject your accusation. If you are unable to take the time to understand how to use copyright law to gain advantage in a commercial society, that's your problem. However it is another thing to cast aspersions on someone to conceal your ignorance in the form of opinion. If you don't want to take my advice, I don't care, if someone uses it to make a long term investment in their career - more power to them.
I'm astounded to hear so many excuses for people to just give up their rights, without even knowing what they are and how to use them.
I wouldn't hire you as a contractor without the ability to fully use, deploy, update and if necessary sell the code you write for me.
I don't care what you do with the code I license to you.
If you want IP ownership over it then we can negotiate on that, but I'm not paying you a licence fee unless you're providing me with a working solution out of the box
That exactly what I have done.
, warrantied
and exactly what I do. I have offered my clients improvements to software I've developed for them. Repeat business.
and with 24/7 support over the lifetime of the software. Good luck meeting my needs on that.
Well its easy to build a straw man and then burn it.
Which is why it costs you five times as much money and time to deploy a software solution and you still end up with technical debt that wouldn't have had if you gotten over the whole *control* issue over my IP and focused on the business outcomes.
I can assure you, I would spend about 20 minutes looking at your business and already know not to waste my time.
I think you have to be crazy to accept such a term as it prevents re-use and is counter-productive to the entity I am contracting to. I point out to them that agreeing to that term prevents me from deploying code I have already written because it provides them a claim over previous works on MY intellectual property that already exist and I deploy.
No it doesn't. If I do work in 2018 for Foo Inc under license X that has precisely zero bearing on stuff I did in 1999 for Barcorp under license Y. How the fuck could it?
Because you've handed over the copyright control of your code to Foo Inc.
So you haven't got the balls to change a contract term during a negotiation? Are you telling me you go to all the effort of reading your contract and you don't negotiated the terms, or that you don't read the contract?
And so are you, snowflake.
Oh sweetie, now you're just being jealous because you regret not standing up for yourself. Do you think they got to be the boss by passively accepting the terms of contracts presented to them? Or were they negotiating terms?
If you're a contractor, being paid for time, you don't usually own anything you produce while you're being paid, it will be in your contract.
So what? With a common law contract (at least where I am) the default position is that the contractor owns the intellectual rights to their code. You have to ADD that condition to a contract to override the common law position.
So with one stroke of the pen, whilst I read the contract, it is gone and the onus is on them to agree or explain why the common law position is not acceptable and we are back to rate negotiations. I think you need to learn some negotiation skills and to not be a pussy. Keep your code and the money. That's what I learned contracting for over a decade, it's money in your pocket.
Isn't it obvious to you they have time and budget constraints if they are seeking a contractor?
They just want to get on with it, if they think you're good enough to offer a contract to then they think you can do the job and don't want to fuck around. You need to foster a business mindset if you are going to contract program they aren't buying code, they're buying time.
If you are a contractor then they don't own your code.
That depends on the contract. Every time I've done contract work, I've signed a "work for hire" agreement, which means the client owns the code I produce. It would be pretty crazy for the client not to require this, in my opinion.
I think you have to be crazy to accept such a term as it prevents re-use and is counter-productive to the entity I am contracting to. I point out to them that agreeing to that term prevents me from deploying code I have already written because it provides them a claim over previous works on MY intellectual property that already exist and I deploy. How would I explain that to a previous employers who didn't ask me to sign away my rights that they could no longer use parts of my code that were used to meet a business deadline because my new employ has a claim on it?
This is a complete deal breaker for me and no contracting programmer should ever agree to such a term, IMO, because you are providing them with a license to use your code in their code, however that doesn't mean they have a claim to my works. If they want to own my code then hire me as an employee or everything for them will be created from scratch. It's not my problem if they can't meet their deadline, I'm here for the money.
Even as an employee you still own the moral right to your code.
Say what? How do you figure that?
Because some rights are unassailable. Even if you have assigned the copyright you are still the creator of the work, that can't change. I think getting a good understanding of the copyright laws (and any local variations) is required reading for any programmers seeking to have a long term, professional career. Don't undermine your own rights, assert them, it's the one thing you can do to improve things for other programmers.
I've written so much code "for me" and for my reuse, this person just leaves me scratching my head. He's written no library work? I'm 40 and I was writing components to reuse back in the 10th grade and started programming in the 4th grade. This person has no excuse for his lack of code.
Precisely, especially if can zero in on what they want you to do. I've got design patterns demonstrated in several languages, like strategy and control in a java script implementation of application controller for front-end stuff because, by all means show them stuff, but you don't want to give them too much as it might be jerks just trying to raid code samples for ideas with no intention of hiring.
If you are a contractor then they don't own your code. Even as an employee you still own the moral right to your code.
Sure, if a candidate handed me thousands of lines of proprietary code and said 'here ya go' that would be a problem but no one is going to chuck a cow about 50 lines of non specific code he'd anonymized to demonstrates a grasp of the language, it's not like he is handing over the plans to the death star.
Having said that, it's not a very classy move. He should be showing better preparation skills and have something that shows he can code a few designs patterns and that he understands why and when to use them. Even better a OSS project.
If you repair it, you won't buy another one. It would be interesting if it stops working if you disassemble and reassemble it *without* doing anything else to it.
Just a few days ago I saw a demo of a script that correctly identified in a video a person that was standing in the shadows and that I couldn't myself identify.
These things were identifying the clothes people were wearing and the mood they were in, and there were hundreds of people in the field of view. Every car license plate, every persons phone number, name and address and if they have a criminal record. I think they being rolled out as 'traffic control devices'
I just want to thank Facebook for it's facial recognition technology that will tag me in enough social situations to make me feel uncomfortable having my photo taken.
Fuck it, if they are going to push all this gender identification and unconscious bias training down my throat then as a 200 pound western man it is my right to identify as a cross dressing islamic woman with a hijab.
Slashdot Mirror
But apart from that he's right, yeah?
Nah, that's just the stuff that is on-topic.
Oh and a correction: That an effect could be transgenic disease that affects the next generation.
Radiation exposure is well understand and extrapolated, and has been for years.
The public risk perception of radiation is so far from reality, it could possibly make us do stupid things.
Your perception of the risk from radiation is so far from reality, you've simplified the model to the point of being useless.
That's been my experience of your posts, that all of the knowledge gathered since the 1950s just doesn't exist. You don't understand :
Then you:
There is a reason the NRC uses ALARA, figuring out this stuff is complicated and the easiest thing to do so your brain doesn't explode from thinking about it is to keep the potential risk of exposure ultra conservative.
In that case, everything you do, even at home, is theirs.
Not unless the contract says so. The contract covers only the contracted work, not everything that you do.
I was not referring to contract work, this specifically refers to "wrote the code as a "work for hire", either as an employee,"
I have seen these clauses, I specifically ask for them to be removed so I know *exactly* what I am signing.
Wow, you are one stupid motherfucker. When 12 different people write a page of a book, who owns the copyright on the page? Later dumbfuck. Better yet, stop wasting my time proving how stupid you are; I get it.
It's ok, we're done here. You have nothing useful to contribute and I'm tired of you trolling me. Sounds like you're having a bad day.
Sure... they'll either offer you less, as you're not given them all that they want, or they'll simply get someone else.
Not when I explain to the project manager how I will meet or exceed their schedule variance and reduce the amount of risks and issues in their project control book. My instinct tells me what buttons to push.
A lot of the time you're not dealing directly with the clients, you get the deal with one of their "preferred vendors" *, who won't/can't negotiate with the terms of the contract, as they have existing contracts with the client.
Different horses for different courses. As always, YMMV.
Is owning the IP to code you write for someone else really important to you?
Not all the time, some code I don't care about. However some code is hyper useful and represents a paradigm shift in my thinking that I use to accelerate other things. Sometimes the ideas are more valuable than the code because I'm going to translate that idea to another language.
So with one stroke of the pen, whilst I read the contract, it is gone and the onus is on them to agree
That's not how contract law works. Unless they initial the change, the presumption will be that they didn't read your alteration, and therefore it isn't binding.
Maybe where you are. I initial the change, I am a signatory to the contract. For them to accept the terms as is, they sign on the dotted line and it becomes binding. I keep a copy and so do they.
Remember, they'll have real lawyers.
So do I.
That being said, they may well agree to the change, especially if you word it such that you'll be using open source code in places, and such code including changes will remain public. Some very big contractors use exactly this approach (and then don't share their changes with the larger community, but that's a different issue).
That's interesting but it sounds like they're violating the GPL when negotiating to maintain copies of my source code that I write and am interested in keeping means we all stay friends and everyone gets what they want. I'm not interested in taking what I haven't written and sometimes I'm not interested in taking what I have written. However taking what is useful to me means they get much more in return.
If you are a contractor then they don't own your code. Even as an employee you still own the moral right to your code.
The most common situation is that you wrote the code as a "work for hire", either as an employee,
In that case, everything you do, even at home, is theirs. If they want to fuck with you and you build something cool and put it out there, they can come after you and claim that what you created is theirs because that is what you have agreed to. You work for them, not for you.
You had better understand what you are signing, it one thing to give your code away, I don't think you would feel the same about having it taken.
or if as a contractor you explicitly assigned the copyrights exclusively to the employer/client.
Well, if you've done that, you have no claim to your IP other than Moral rights of attribution.
I don't know what country the OP is from, but speaking to those in the USA, could you provide some explanations (and legal citations to support them) about "moral rights" and how this would allow you to give that code to someone else such as a potential new employer?
Local legislations vary, which is why I say you have to take personal responsibility for knowing the law where *you* are. If he under a NDA, nothing. If he has assigned copyright, nothing. He could argue fair use to assert his moral rights of attribution to show code he created, however YMMV depending where you live. Failing that his moral rights are 'yes he worked on that project'.
Cuz I don't think you can.
Introducing: The Berne Convention, I've explained there.
I did no such thing to confirm your ignorance. You skipped over the part where I challenged you: I employ a lawyer to ensure I meet my legal obligations ... What do you do?, the obvious answer is, nothing.
The US is a signatory to the Berne convention. As programmers I think your country has specifically given up some of the rights you had to the MPAA simply because you did not defend your rights. I don't specifically know what your situation is wrt local laws because as I said: I am saying what is legal for me, where I am. You have to take responsibility for yourself.
Seems like you didn't and the truth hurts you so much you're willing to falsify your own reality so you maintain ignorance about what you have lost evidenced by the contempt you are projecting onto me.
I don't see where I made a claim to be super smart, only that I've retained a lawyer and reseached enough about copyright law to protect my rights. I write and record music, I had to learn. When I did I found it applied to the software I wrote. Instead of decending into responding to your emotive outburst and abusing you, let's re-visit the comments I made that everyone seems to have a problem with:
If you are a contractor then they don't own your code. Even as an employee you still own the moral right to your code.
Specifically, if you are a contractor then you own the copyright to your code unless you agree to contractual terms to give up those rights. Anyone with sufficient deductive reasoning should be able extrapolate their legal situation to a corporate entity that has exactly the same set of rights that you do. The difference is they are negotiating from a position of strength so that you will relinquish your rights. But let's not let logic get in the way of me demolishing this "argument" with the relevant facts.
First, Article 10 of The TRIPS Agreement contains an interpretive provision stating that computer programs, whether in source or object code, shall be protected as "Literary Works" by the Berne Convention. Article 4 of the 1996 WIPO Copyright Treaty (WCT) includes a clarification in very similar terms.
Article 6 and Article 7 of the WCT document determine the framework for negotiation. You give up your rights according to WCT 6(2), I maintain my rights according to WCT 6(1) and WCT 7(1,3).
Therfore source and object code are protected as 'Literary Works' under Article 2 of the Berne Convention as original works and nothing in that treaty applies to you submitting your source code to a larger tree negates that right unless you specifically give it up. Specifically Berne Article 2(1,3,5), limited by local legislation which is why I say you need to take personal responsibility for knowing your local laws.
Second, as to Moral Rights, this is the specific position of the OP covered in
> If you are a contractor then they don't own your code.
Jesus, what? Contractors don't own their own code, you're really badly misinformed.
Your post makes not sense.
I get it that people are afraid to stand up for their own rights and haven't learned how to do that, however for you to make a joke about it makes you come off as a coward, Courageous. Is that what you are telling me?. Do you think I'm going to laugh with you and say 'Gee, shucks, I guess I should give up my rights the same way you do and disappear into the banal'. Perhaps I just don't understand the desire for subservience in place of respect.
I see a lot of people here arguing to make their position weaker with employers because they are too mentally lazy to take personal responsibility for their own education in the copyright law that affects them. I've no doubt these people are also complaining about H1B visas as well. Obviously they're not the rock stars they thought they were.
By all means stay where you are comfortable, and complain that no-one stood up for your rights so you can feel that satisfaction of being like everyone else. Don't worry, someone else will take your share and you will give it up without complaint because you don't deserve it. Frankly, it's a pathetic sign of mediocrity to be criticized by sheep for not being a sheep and I'm so happy not to have been stained by it.
If the horror of me sharing how I stand up for my rights is too much for you, then the thought of how I am going to apply Software Patents will be stuff of nightmares for a long time. Whilst you struggle to figure out how to use your rights, I'll be working on extending them. This thread has been unexpectedly educational, I'm certain I won't be the only one using this knowledge to derive maximum strategic value from it in their next contract negotiations.
Thanks. It's crazy, they're actually arguing to make themselves weaker. Next week they'll complain about H1B visas and how no one stood up for them.
It is not true that they don't own the code if you are a contractor unless you have that in writing.
Really? So you know all regions, all legal jurisdictions? I am saying what is legal for me, where I am. You have to take responsibility for yourself. I employ a lawyer to ensure I meet my legal obligations and make sure I'm educated enough to negotiate. She has a safe with year on year copies of my codebase all they way up to my local statute of limitations. What do you do?
Some people think it is not moral to violate the law, so if anyone follows your advice they will be doing something that is possibly unlawful and certainly morally ambiguous at best.
You accuse me of moral ambiguity yet you demonstrate no clear understanding of the legal premise behind 'Moral Rights'. Anyone who takes personal responsibility for understanding what their rights are and then uses them is doing what a capitalist society encourages us to do, indeed, what it is there for. My morality is making sure I do what is legal.
My code is a business. I reject your accusation. If you are unable to take the time to understand how to use copyright law to gain advantage in a commercial society, that's your problem. However it is another thing to cast aspersions on someone to conceal your ignorance in the form of opinion. If you don't want to take my advice, I don't care, if someone uses it to make a long term investment in their career - more power to them.
I'm astounded to hear so many excuses for people to just give up their rights, without even knowing what they are and how to use them.
I wouldn't hire you as a contractor without the ability to fully use, deploy, update and if necessary sell the code you write for me.
I don't care what you do with the code I license to you.
If you want IP ownership over it then we can negotiate on that, but I'm not paying you a licence fee unless you're providing me with a working solution out of the box
That exactly what I have done.
, warrantied
and exactly what I do. I have offered my clients improvements to software I've developed for them. Repeat business.
and with 24/7 support over the lifetime of the software. Good luck meeting my needs on that.
Well its easy to build a straw man and then burn it.
Which is why it costs you five times as much money and time to deploy a software solution and you still end up with technical debt that wouldn't have had if you gotten over the whole *control* issue over my IP and focused on the business outcomes.
I can assure you, I would spend about 20 minutes looking at your business and already know not to waste my time.
No it doesn't. If I do work in 2018 for Foo Inc under license X that has precisely zero bearing on stuff I did in 1999 for Barcorp under license Y. How the fuck could it?
Because you've handed over the copyright control of your code to Foo Inc.
Yeah, that's why they do that.
So you haven't got the balls to change a contract term during a negotiation? Are you telling me you go to all the effort of reading your contract and you don't negotiated the terms, or that you don't read the contract?
And so are you, snowflake.
Oh sweetie, now you're just being jealous because you regret not standing up for yourself. Do you think they got to be the boss by passively accepting the terms of contracts presented to them? Or were they negotiating terms?
They respect that you've got some balls.
If you're a contractor, being paid for time, you don't usually own anything you produce while you're being paid, it will be in your contract.
So what? With a common law contract (at least where I am) the default position is that the contractor owns the intellectual rights to their code. You have to ADD that condition to a contract to override the common law position.
So with one stroke of the pen, whilst I read the contract, it is gone and the onus is on them to agree or explain why the common law position is not acceptable and we are back to rate negotiations. I think you need to learn some negotiation skills and to not be a pussy. Keep your code and the money. That's what I learned contracting for over a decade, it's money in your pocket.
Isn't it obvious to you they have time and budget constraints if they are seeking a contractor? They just want to get on with it, if they think you're good enough to offer a contract to then they think you can do the job and don't want to fuck around. You need to foster a business mindset if you are going to contract program they aren't buying code, they're buying time.
If you are a contractor then they don't own your code.
That depends on the contract. Every time I've done contract work, I've signed a "work for hire" agreement, which means the client owns the code I produce. It would be pretty crazy for the client not to require this, in my opinion.
I think you have to be crazy to accept such a term as it prevents re-use and is counter-productive to the entity I am contracting to. I point out to them that agreeing to that term prevents me from deploying code I have already written because it provides them a claim over previous works on MY intellectual property that already exist and I deploy. How would I explain that to a previous employers who didn't ask me to sign away my rights that they could no longer use parts of my code that were used to meet a business deadline because my new employ has a claim on it?
This is a complete deal breaker for me and no contracting programmer should ever agree to such a term, IMO, because you are providing them with a license to use your code in their code, however that doesn't mean they have a claim to my works. If they want to own my code then hire me as an employee or everything for them will be created from scratch. It's not my problem if they can't meet their deadline, I'm here for the money.
Even as an employee you still own the moral right to your code.
Say what? How do you figure that?
Because some rights are unassailable. Even if you have assigned the copyright you are still the creator of the work, that can't change. I think getting a good understanding of the copyright laws (and any local variations) is required reading for any programmers seeking to have a long term, professional career. Don't undermine your own rights, assert them, it's the one thing you can do to improve things for other programmers.
I've written so much code "for me" and for my reuse, this person just leaves me scratching my head. He's written no library work? I'm 40 and I was writing components to reuse back in the 10th grade and started programming in the 4th grade. This person has no excuse for his lack of code.
Precisely, especially if can zero in on what they want you to do. I've got design patterns demonstrated in several languages, like strategy and control in a java script implementation of application controller for front-end stuff because, by all means show them stuff, but you don't want to give them too much as it might be jerks just trying to raid code samples for ideas with no intention of hiring.
If you are a contractor then they don't own your code. Even as an employee you still own the moral right to your code.
Sure, if a candidate handed me thousands of lines of proprietary code and said 'here ya go' that would be a problem but no one is going to chuck a cow about 50 lines of non specific code he'd anonymized to demonstrates a grasp of the language, it's not like he is handing over the plans to the death star.
Having said that, it's not a very classy move. He should be showing better preparation skills and have something that shows he can code a few designs patterns and that he understands why and when to use them. Even better a OSS project.
Any more than that and you're not succinct.
Now tell me, how else are you going to kick that if not with a foot?
Here is a quick guide.
Drugs are bad, mmmkay.
If you repair it, you won't buy another one. It would be interesting if it stops working if you disassemble and reassemble it *without* doing anything else to it.
Just a few days ago I saw a demo of a script that correctly identified in a video a person that was standing in the shadows and that I couldn't myself identify.
These things were identifying the clothes people were wearing and the mood they were in, and there were hundreds of people in the field of view. Every car license plate, every persons phone number, name and address and if they have a criminal record. I think they being rolled out as 'traffic control devices'
Orwell was an optimist.
I just want to thank Facebook for it's facial recognition technology that will tag me in enough social situations to make me feel uncomfortable having my photo taken.
Fuck it, if they are going to push all this gender identification and unconscious bias training down my throat then as a 200 pound western man it is my right to identify as a cross dressing islamic woman with a hijab.
Have you seen these AI augmented camera arrays? They are about the most frightening thing I have ever seen.
Interesting too, thanks for the advice.