2 ms·
That is fine, just be upfront about it. Still require a contract for it is reeking of trying to get work for "free". If you have it running in production, and u
by hvidgaard 9y ago
That is fine, just be upfront about it. Still require a contract for it is reeking of trying to get work for "free". If you have it running in production, and use it because you understand it thoroughly, it shouldn't matter what the candidate comes up with. Any new insight he might bring you can always incorporate with your own code. In any case none of the code is expected to be used in production, and if it turns out you want to, it's probably the candidate you want to hire anyway.
- gowld 9y ago> Any new insight he might bring you can always incorporate with your own code Only if the contract is signed.
- hvidgaard 9y agoIf you want to use the candidates code, then you have to have a signed contract. Nothing prevents you from looking at the code, and write your own version of it.
- danpalmer 9y agoYep I agree. Just a minor bit of friendly feedback on your comment, I hope you don't mind... You said "Any new insight he might bring". To refer to a hypothetical developer as "he" contributes to the stereotype of developers being male, and that can make those who don't conform to that feel less welcome in the community. I'm sure this wasn't a conscious decision, and I know it's something I slip up with frequently, but I'm trying not to do it, and I think writing that is more inclusive is more persuasive to more people and generally better.