4 ms·
I may be naive, but I don't think professors would typically do that, certainly not if you offer them to be a co-author in exchange for professionalizing the pa
by Someone 9y ago
I may be naive, but I don't think professors would typically do that, certainly not if you offer them to be a co-author in exchange for professionalizing the paper (which may mean serious work, e.g. to benchmark the algorithm against other algorithms for speed and accuracy). Even if you don't offer that, they will have a few months to work on follow-up papers (e.g. on I mplementing it on GPUs, in parallel, or on simple architectures)
You can also publish (e.g. by tweeting it) a hash (a few different hashes, if you are truly paranoid) of your code before going to said professor. That gives you some leverage against appropriation, as it would allow you to prove you knew about the approach at a given time.
If you combine it with some context ("going to meet X to discuss 0xA43AF7F963DA003F"), that leverage gets larger. I wouldn't know whether either would be enough, though. There likely is little jurisprudence on things like this, it may be costly to go to court over it, and using it out of court, e.g. by writing to any journal publishing this without your name on it, may backfire)