Re^2: How can you protect your Perl Mods/Hacks?

[jettero]

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

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).

[diotalevi]

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.'

[bart]

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. :)

[diotalevi]

No, that was someone who didn't hire me but who also hadn't ever heard of CPAN. They just weren't a player.

[fenLisesi]

What, stunnix hired you?

[diotalevi]

Nah! Didn't you know? I went into business as an obfuscator myself! I use the magic of uudecode!

*wink*