Hmm. I'm for open code broadly but good testing of output is cheaper & much more doable than catching cheating in millions-of-line codebase.
-
-
Replying to @zeynep
For VW, most likely to work and scalable solution was proper testing in the wild. DMCA shutting of research is bad but... this is also true.
1 reply 1 retweet 1 like -
Replying to @zeynep
As more objects get code, I don't see how we get a scaleable army of people figuring out all the messy code. But we can always test outputs.
2 replies 1 retweet 2 likes -
Replying to @zeynep
Also, umm, people who write original code can't sometimes figure out what that subroutine exactly does.

Reverse engineering isn't easy.3 replies 1 retweet 3 likes -
Replying to @zeynep
@zeynep Can obfuscate source in non-obvious ways: http://www.se.rit.edu/~tabeec/RIT_441/Resources_files/How%20To%20Write%20Unmaintainable%20Code.pdf …1 reply 0 retweets 0 likes
@IanDavey773 "Ensure a job for life ;-)" hahahaha. I fixed code like that. Bleargh.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.