Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Include a copyright statement reserving all rights to the code. Make it clear to the person receiving this that this code is allowed to be viewed and evaluated only. If they start using your code, and you can prove it, you can make a copyright claim. It is theft no matter how you look at it. Service theft is also punishable in local municipalities. Know your local laws.
-
Is there a software license template for this?
Something like:
"This code copyright John Smith 2020. All rights reserved.
If you are a potential employer you have n days to review this code for quality and efficacy. After which this temporary license expires."
Could even have an end date inserted in there. You could even embed a phone home line of code to tell you if they are running your code. -
@Demolishun sounds good. But wouldn't it be too hard to check whether they used your code or not? Then you would have to file for the right to scan *all* their source files for matching patterns or something?
Edit: nowhere near experienced with laws, but I find this quite interesting how someone could protect their code from these things -
@NEMESISprj I don't know, but at least you show your intent and gives you grounds to hold them accountable. If they are completely amoral they won't care anyway. If they are too dumb to code it themselves they may not have the brains to check for phone home stuff. This could at least be an avenue for proof. Now, lets say they do this to 100 coders. Could be grounds for class action suit. Which could be devastating and send a message to other douche bag companies. But, this all costs money. So I don't know the reality of this paying off.
-
@Demolishun yeah when you get in contact with bigger companies it's probably not worth the effort other than going public with it or smth.
The ultimate payback would be to create backdoors in your code for these kinds of tests lol -
@Demolishun yeah not the best way to show a company that you want to work for them
Stackoverflow.
For those of you who are having interviews ... remember this
Just had my reasoning for not doing technical projects for interviews proven.
Pass the first 2 stages of interview (including showing some personal portfolio projects) then after a week of hearing nothing get sent a technical project to complete.
Spend every spare moment for a week polishing this thing, decent front end, quick and efficient back end, low traffic between fe, be, persistence etc.
Submit the code at midday ready for the interview the following day, only for the company to phone at 5pm and say all is fine and the code is great for the final interview (walkthrough) the next day, then phone 5:10pm phone and pull the position.
That company has just had free work done which should have cost 1 weeks worth of fees, using the premise of a job at the end of it, only to take the code that they are super happy with and run with no payout.
rant
free work
interview
tech test
free loading