Along these lines would be publishing your sacred hacks as early as possible so you can always point to the earlier timestamp: See!?! I did that! Then the copying is ordinary plagiarism. IMO, if your code is reasonably good and readable, it helps you get interviews down the road — some employers really do review your stuff before they bring you in.
But, concerning the grandparent post, I think a better model for making cash on plugins like this would be feature requests. I believe you can pay for votes at vim.org (for example).
-Paul
In reply to Re^2: How can you protect your Perl Mods/Hacks?
by jettero
in thread How can you protect your Perl Mods/Hacks?
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |