product

IT Product design when left in the hands of the developer tends to include everything the programmer, or the team thereof, is capable of accomplishing. As a result the product tends to have many Swiss Army knife type features, but lacks any real cutting edge, since the development time gets distributed around many small features while the main functionality does not get enough attention to be robust and mature (read fault tolerant, adaptible, portable, et cetera.) The latest technology article on HBR, Feature Bloat succintly discusses this phenomenon and its cures:

Way back in 2001 end, when I interacted with Marc Fleury, the dynamic Founder of JBoss, I was having a fair idea about the destiny of JBoss.

A seven plus years journey for JBoss has not been a smooth ride in the early days of skepticism surrounding Java Open Source and J2EE certification issues.

Finally after much speculation about Oracle's possible new item in its long shopping list, JBoss made RedHat its new container!

Here is how JBoss would look like now on http://www.redhat.com/about/news/prarchive/2006/jboss.html

This has been going in my mind for over 5 years within. Should a nation with more than a billion bodies be busy coding for billing or need to seriously innovate to develop to distribute?

I think I found the answer in Samooha http://www.samooha.com. Develop to distribute is the best way to go forward. It would not only be in the interest of a nation that is emerging out of woods but also would be in the greater interest of a balanced world.

Now bloggers have a greater role to play in shaping the destiny of "Develop 2 Distribute" through Samooha!