Monday | 8 September, 2008
Computerworld
What to do when developers take code snippets with them
When developers carry toolboxes full of code from job to job, intellectual property implications get hairy
Bill Snyder (InfoWorld) 18/04/2008 08:12:11

Computerworld Buyer's Guide - Vendors Matched to this Article
Additional Resources
Executive Guides
Whitepapers
Zones
Zone logoZones provide focussed content from Computerworld and leading technology partners.

Newsletter Subscription

Sign up for our Computerworld newsletters!
Computerworld's twice-daily news service keeps you in touch with the latest, most important headlines from Australia and around the world.
Keep up with the latest virtualisation technologies, products, news and features.
RSS Feeds

IP purity is gaining the attention of developers who work with the US Department of Defense, which is using more and more open source software, despite some bureaucratic misgivings. One roadblock: the lack of a highly developed and widely recognized governance regime for open source, said Brigadier General Nickolas Justice, in a recent interview with Military Information Technology.

The Multinational Information Sharing Initiative (MISI), for example, is part of a DoD effort to share counterterrorist information among the nine countries of trans-Saharan Africa. MISI, which will also have many nonmilitary uses, was deliberately built around open source to make it easy to deploy by organizations within those countries that might balk at the hefty licenses fees charged by commercial software vendors, says Bernard Golden, CEO of Navica, which developed a governance framework for the project.

"To work with open source, you have to adhere to the letter and the spirit of the license," Golden says. Sure, that seems obvious, but MISI has to keep track of 60 or so open source products while being careful not to let unlicensed software slip into the code base. Unknown code also creates a support problem, Golden adds. After all, without knowing the provenance of the code, how can a support engineer identify and fix a problem?

Because Protecode and its competitors are privately held, it's not clear how much, if any, money they are making. A point in their favor is the relatively high bar for entering the market. The real value is in the database, which takes years to accumulate. The code itself is not that difficult to assemble, says Venugopalan.

Also unclear is the effect that HP's code analysis tool will have on the trio. It's available for download at the FOSSology Web site. What is clear, though, is the continuing development of the open source ecosystem. The stronger it gets, the more likely it is that the remaining doubters in the Pentagon and mainstream business will come aboard.

Computerworld Buyer's Guide - Vendors Matched to this Article

Comments

Where is the line drawn?

Bill,

Interesting article about how developers take code from one company to the next. Of course any kind of copying of code is an automatic infringement on copyright, but there is a far more insidious implication that goes unnoticed in your article.

Lets say I work for company A, and they ask me to build something for them. As part of what I create I use a certain technique that I find works very well. I move on to company B who ask me to build something for them. I find that the same technique I used with company A would work just as well for company B....

What do I do?

Do I avoid the technique altogether because it would infringe on the IP of the company I was at when I created it? Do they own the technique itself or just the implementation? If I use my memory to re-code using the same technique (ie no direct copying of code done) am I breaching their IP? Or am I wasting company B's valuable time and resources by re-inventing the wheel the 10th time over by trying to use my memory to reconstruct the same thing I have created everywhere else?

You could look at two implementations using the same technique and see they were not copied, yet you could see similarities that are significant enough that some people may say its the same thing. Is it considered a pattern and thus not copyrightable? Do I call it MY pattern and put my own patent on it to stop others from using it? Can I put a patent on something which is a technique for doing something?

While some of these techniques may be broad enough to be non-specific (Factory, Controller, Facade, etc), other techniques are fairly specific yet highly re-usable across projects. As a developer I keep seeing a need for a certain implementation, so I keep re-inventing the wheel everywhere I go. Does intellectual property cover the "nuts and bolts" of programming or the use of it as a whole?

I can't help but feel that I am wasting their time by repeating the same thing over and over again when I already know the generic one I created previously already works. What if the new version of it that I coded from my mind misses some vital component? Am I not doing more of a disservice to the customer by NOT re-using code that I know has been tried and tested over and over again by creating something that tries to use my memory to reconstruct the principle?

Surely having a "toolbox" of useful code snippets which you know as a professional is already well tested and encapsulated, as well as being suitable for the purpose is a benefit to any company you bring it to. What I fear is that I do this "favour" for a company, and in return they try to take it off me by claiming it is now their intellectual property, when in reality I could have saved several hours of their time by not re-coding it from memory and costing them money in the process.

Market Place

Computerworld Member Login


 

Prioritizing Services with IT Service Management (ITSM)

Computerworld Live Webinar
Wednesday 20th, August 2008
11:00am EST (Sydney, Australia)

To be repeated on:

Thursday 4th, September 2008
11:00am EST (Sydney Australia)

Sign up and receive a free copy of The Forrester WaveTM Service Desk Management Tools, Q2 2008 at the conclusion of the Webinar.

Attend and discover:

  • How to deliver value to your business through ITSM
  • Best practice ITSM implementation
  • Why emphasis is changing from optimizing IT management processes to better servicing customers and demonstrating real dollar value
  • If service-oriented ITSM is best for your business
Whitepaper

Still Sneaking In: The Threats Your Security Tools Aren't Telling You About

Web 2.0 applications are all the rage, offering us tremendous value when it comes to collaboration and communication. They also open us up to new kinds of attacks however, and can cause problems in keeping systems and data secure. Read on to learn about the new attack methods and how you can defend yourself and your business.

Enterprise IT Buyer's Guide
Find Technology Vendors Fast
 
Find vendors by name | Find by category
Sponsored Links