Opening up source code

Some good pointers to consider making a close source effort to open source. Here is an example of Ingres and how it transition from close source to open source.

Key points – and SCO/Unix fight has contributed to this learning.

• Comb every line of the source before opening it up and remove questionable references/code snippets
• Pick the right open source licence
• It takes some promotion and effort to attract open source community
• Security concerns are not any more vulnerable in Open Source than Close Source (Re-engineering usually attributes to similar security vulnerability than what one may find reviewing the source)

I would probably add following to the list:

• Understand business need. Both Closed Source and Open Source (or a combination) has its merit – so understand what problem is being tackled by opening the source
• Consider what open community suits the need and how it helps the community
• Consider business model and structural changes required 
• Consider the stage of product life cycle

Fake cloud?

I liked this blog entry on 15 ways to tell it is not cloud. Among them, I liked these the most:

• If they are trying to sell you hardware… its not a cloud.
• If there is no API… its not a cloud.
• If you need to re-architect your systems for it… Its not a cloud.
• If it takes more than ten minutes to provision… its not a cloud.
• If it only runs one operating system… its not a cloud.

One thing, I would have added to the list and see cloud succeed:

• If you can’t transfer your existing software licence… its not a cloud.

Cloud computing is maturing and progressing well. It continues to become reliable and available at cheaper cost than businesses otherwise would spend. Time will tell its success. One trend to observe will be small-mid businesses broadly adopting cloud to run businesses-critical core applications beyond adjacency services.

Innovation stumbling block

Innovation is hard. It is usually hard in an established organization. Why?

Top 3 reasons, in my mind, that hurt innovation in an established organization:

1. Knowledge – It is a double edge sword. While past experience helps but many smart brains get caught up to the learning or failed experiences of the past talking themselves (and unfortunately others too) out of good ideas prematurely.

2. Being perfect – On the other end, smart people looking for the perfection doesn’t help either.  Smart folks finding themselves rat-holing a conversation on obscure things making an idea too hard to conceive at the onset or too costly to tackle. Some time perfect is the enemy of good enough that stop conceiving a great idea from taking shape. Innovation evolves by shaping the idea one day at a time to its greatness.  

3. Afraid of failing – Smart people trying not to stick the neck out or taking chances that may make a difference because the potential of an effort may fail. It is our desire to act ordinary and remain on the proven path hence avoiding what best could have been achieved. It is amazing how conspiracy theorists (and they exist) attract smart brains keeping them just acting ordinary.