in reply to How can you protect your Perl Mods/Hacks?

You could possible compile some of your code, which would mean he'd need to reverse engineer it. But in all honesty this kind of thinking is not going to get you very far in the perl community. How many other people do you see selling perl libraries? And if there was any kind of demand for the thing you were creating, it would be on CPAN already. Even if it isn't, there's enough of a DIY ethic around here that somebody else will quickly duplicate your work.
  • Comment on Re: How can you protect your Perl Mods/Hacks?

Replies are listed 'Best First'.
Re^2: How can you protect your Perl Mods/Hacks?
by jettero (Monsignor) on Apr 09, 2007 at 18:05 UTC

    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

[reply]

      It happened to me. I hear it was one of the things that helped my current employer decide I was a good prospect. Shortly after they'd gone and read my stuff on CPAN they flew me in for an on-site interview. Twas 'woot.'

      ⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊

[reply]
        I'm glad it eventually turned out that way. I rememebr you complaining that a previous (possible) employer thought nothing of your Perl skills, after all, you had never been employed as a (full-time) Perl developer before. I remember you were very disappointed, and down, about the whole thing.

        I hope I'm not misrememebring, or otherwise misrepresenting anything. :)

[reply]
[reply]

In Section Seekers of Perl Wisdom