Comments on: Signing your code. http://ikeif.net/2008/06/05/signing-your-code/ iKeif.net - Web developer, father, and brewer. Sat, 05 Jun 2010 04:20:35 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: keif http://ikeif.net/2008/06/05/signing-your-code/comment-page-1/#comment-39 keif Fri, 06 Jun 2008 04:00:20 +0000 http://ikeif.net/?p=92#comment-39 I think that's just it - leveraging group intelligence. I'm glad that businesses (and people) are realizing that constantly reinventing the wheel is a foolish, redundant process. I think that’s just it – leveraging group intelligence. I’m glad that businesses (and people) are realizing that constantly reinventing the wheel is a foolish, redundant process.

]]> By: Matt Sidesinger http://ikeif.net/2008/06/05/signing-your-code/comment-page-1/#comment-38 Matt Sidesinger Thu, 05 Jun 2008 13:13:50 +0000 http://ikeif.net/?p=92#comment-38 Vimeo has a little something at the top of all of their pages. Meebo has this little gem: <!-- interested in joining meebo? we have full time and internship opportunities available including front-end software engineer (JavaScript/DHTML/Ajax/C/C++), back-end software engineer (C/C++/networking/databases), and visual designer. email secretjobs at meebo dot com with your resume and cover letter. thanks! --> Vimeo has a little something at the top of all of their pages.

Meebo has this little gem:

]]> By: Andrea Hill http://ikeif.net/2008/06/05/signing-your-code/comment-page-1/#comment-37 Andrea Hill Thu, 05 Jun 2008 08:43:36 +0000 http://ikeif.net/?p=92#comment-37 Great post, Keith. I like the idea of contributing back to the community. Do you remember for the longest time there were all these hacks to prevent someone from looking at your source code? I consider it similar to some of the recent discussions about intellectual property and "who owns what you blog about". However, it seems to me the idea of "Drawing inspiration" (or downright copying) work when you're a professional can be tricky business. At LexisNexis, we had to go through a formal process to eve consider using third party code libraries (even if they were freely offered on the web). The notion is that if you're a professional, you should be paid for your unique work, not being a good googler. On the flip side, however, is the notion of best practices, standards, leveraging group intelligence and just working smarter. I think it's a sign of maturity to look at how others have solved a problem before just diving in to reinvent the wheel. Again, thanks for the thoughts... Great post, Keith.
I like the idea of contributing back to the community. Do you remember for the longest time there were all these hacks to prevent someone from looking at your source code? I consider it similar to some of the recent discussions about intellectual property and “who owns what you blog about”.
However, it seems to me the idea of “Drawing inspiration” (or downright copying) work when you’re a professional can be tricky business. At LexisNexis, we had to go through a formal process to eve consider using third party code libraries (even if they were freely offered on the web). The notion is that if you’re a professional, you should be paid for your unique work, not being a good googler.
On the flip side, however, is the notion of best practices, standards, leveraging group intelligence and just working smarter. I think it’s a sign of maturity to look at how others have solved a problem before just diving in to reinvent the wheel.

Again, thanks for the thoughts…

]]>