Handling licensed and permitted code reuse fairly

From Codequiry, 1 Month ago, written in Plain Text, viewed 1 times.
URL https://stikked.z-apps.ca/view/015814b8 Embed
Download Paste or View Raw
  1. Handling licensed and permitted code reuse fairly
  2. =================================================
  3.  
  4. This is a working note on handling licensed and permitted code reuse fairly: what held up over several terms, what quietly stopped being done, and which of those two was actually a problem.
  5.  
  6. Deciding what the output is for
  7. -------------------------------
  8. Distinguish between code that is similar and code that shares a history. Two implementations of the same textbook algorithm are similar and unrelated. Two files with the same unusual variable ordering, the same dead branch and the same off-by-one comment share a history. Systems that report only the former make the reviewer do the work of finding the latter, on every single pair, forever.
  9.  
  10. What the reviewer actually needs
  11. --------------------------------
  12. Publish the method to the people being measured. Students and candidates who know what is compared, against what, and what happens next behave differently from those who do not — and the difference shows up as less of the thing you were detecting. Detection and deterrence are not in tension here; secrecy about the method buys a marginally higher catch rate and gives up nearly all of the deterrent effect.
  13.  
  14. Making it survive the year
  15. --------------------------
  16. Version the corpus, not just the code. A comparison run in March against a corpus that has since grown cannot be reproduced in June, and "we re-ran it and got a different number" is a sentence that ends processes. Recording which snapshot a result came from costs a column in a table, and is the difference between a finding that survives review and one that evaporates under it.
  17.  
  18. Putting it into practice
  19. ------------------------
  20. What separates a source code plagiarism detection from a diff is that it can tell you what the overlap means.
  21.  
  22. Reference: https://codequiry.com
  23.  

Reply to "Handling licensed and permitted code reuse fairly"

Here you can reply to the paste above