Usually I am the type of person who never bought any thing without purpose, or never keep desire about the thing that is not able to enhance my lifestyle. Due to that behavior I never felt any necessity for iPod in my simple lifestyle.
But once my one friend Sharad Katiyar explains me the features associated with iPod and also explains me the various benefits I can achieve if I had an iPod. So after listening to him very consciously I also felt some need (with unwillingness) for iPod in my life.
But before finalizing the purchasing of iPod, I wanted to satisfy myself first. For that reason I went to Apple Store in Market. I tried to get the trial for an iPod, but could not felt satisfaction and hence I give-up the idea about purchasing the iPod.
But few week back, client itself given iPod to me as a reward for completion of product development. I have just opened yesterday and since then I am continuously listening it. It felt so good. I guess only reason for change of my mind is, on trial I was listening English songs instead of Hindi, which I am listening from yesterday. :)
Thursday, May 12, 2005
Sunday, May 08, 2005
Issues of startup organization
I have got the chance to work in start-up in USA. Company is working in IP Telephony System. And now after working for last 3 years they are about to release their product. I tried to understand the reason why their product fails earlier. I found some interesting points behind that.
First point is selecting the right technology to implement the product. Company tried to prepare the product in C++/VC++ earlier. But as every one knows C++/VC++ is good for client server application where there are so much involvement of users comes in. But if application requires several layers, J2EE is getting advantage over C++/VC++. As lot of complex job, is being done already by several frameworks freely available in the Market.
So company could not prepare the first version of product with help of C++/VC++ in their first year. Then realizing the power of J2EE technology they tried to use that for preparing the product. Since then they are working with J2EE technology for making it better.
Next point is about the Architecture. A good architect product is always easy to implement and maintain. Company’s second version (J2EE product) of product fails due to bad architecture.
And third point comes the outsourcing. Amazing!! Don’t believe it. Me too! I could not believe that any startup would try to outsource their part of product. But due to saving money on user interface, as hiring a user interface guy here may be costlier to them. But they didn’t realize that being as a startup, when things hardy clear to everybody, they should not outsource any part of process to other company. And that was third failure for them.
Getting continuous third failure, now company has been much mature, and they realized the importance of technology, architecture and management of the product. So they hire New VP, New Architect and few very good technical people. So they can reduce the time of product formation.
Besides that company also thought about the coverage part. Earlier they had tried to cover everything in one go. Now they realize the complexity of that and decided to move gradually. And that decision provides them another step to success of their product.
Now company is able to release their product and trying to enhance the coverage of that product. Some another form of issues is coming into the picture. And those are related with managing the growing team. Although nothing serious as of now but may impact in future.
Now as company is having sufficient of resources and they are growing as per time. Still some people are working in the company for longer than years; Old resources are being possessive about the part they have completed. And this possessiveness doing harm to whole product without unknowingly. Due to that another issue is being arising is lack of distribution of role, authority and responsibility, particularly in their quality process. Still they are not realizing the quality process for their product. I am pretty sure after some time it will going to cost them big.
First point is selecting the right technology to implement the product. Company tried to prepare the product in C++/VC++ earlier. But as every one knows C++/VC++ is good for client server application where there are so much involvement of users comes in. But if application requires several layers, J2EE is getting advantage over C++/VC++. As lot of complex job, is being done already by several frameworks freely available in the Market.
So company could not prepare the first version of product with help of C++/VC++ in their first year. Then realizing the power of J2EE technology they tried to use that for preparing the product. Since then they are working with J2EE technology for making it better.
Next point is about the Architecture. A good architect product is always easy to implement and maintain. Company’s second version (J2EE product) of product fails due to bad architecture.
And third point comes the outsourcing. Amazing!! Don’t believe it. Me too! I could not believe that any startup would try to outsource their part of product. But due to saving money on user interface, as hiring a user interface guy here may be costlier to them. But they didn’t realize that being as a startup, when things hardy clear to everybody, they should not outsource any part of process to other company. And that was third failure for them.
Getting continuous third failure, now company has been much mature, and they realized the importance of technology, architecture and management of the product. So they hire New VP, New Architect and few very good technical people. So they can reduce the time of product formation.
Besides that company also thought about the coverage part. Earlier they had tried to cover everything in one go. Now they realize the complexity of that and decided to move gradually. And that decision provides them another step to success of their product.
Now company is able to release their product and trying to enhance the coverage of that product. Some another form of issues is coming into the picture. And those are related with managing the growing team. Although nothing serious as of now but may impact in future.
Now as company is having sufficient of resources and they are growing as per time. Still some people are working in the company for longer than years; Old resources are being possessive about the part they have completed. And this possessiveness doing harm to whole product without unknowingly. Due to that another issue is being arising is lack of distribution of role, authority and responsibility, particularly in their quality process. Still they are not realizing the quality process for their product. I am pretty sure after some time it will going to cost them big.
Thursday, May 05, 2005
Good lesson from real life activities
Yesterday, Suddenly we got to know that VP Engineering of my client company has been asked to leave. The reason described by one of the Board Of Directors was, As Client is looking for VP having more technical back ground in which client company is working.
It was a shock for the all of the engineering team who works with VP including me. The reason for shocking was even more intresting. Current VP was the first one under which client company was able to deliver good quality product. Before that client company was struggling since last 3 years to deliver a product upto market expectation.
Apart from responsiblity of delivering good product, current VP was also responsible for maintaining healthy envoirnment of work and prepare a team to do the work. VP has made significant improvement on these in very short duration. Infact i have also sensed those improvement in duration of 3 month only.
As i am here due to sheer intrest of VP. It would quite possible that i may also asked to leave after certain time when contract period will be over.
I have learned two lesson from this incedent:
1) Never disclose your cards to upper management unless you are not part of them.
2) Always create situation where you are needed most. As soon as you are no longer needed, you will be kicked out.
So In summary, lesson is, don't do good work unless you are not sure that you are going to get benefit of the work you have done!
That's why i hate to be in management.:)
It was a shock for the all of the engineering team who works with VP including me. The reason for shocking was even more intresting. Current VP was the first one under which client company was able to deliver good quality product. Before that client company was struggling since last 3 years to deliver a product upto market expectation.
Apart from responsiblity of delivering good product, current VP was also responsible for maintaining healthy envoirnment of work and prepare a team to do the work. VP has made significant improvement on these in very short duration. Infact i have also sensed those improvement in duration of 3 month only.
As i am here due to sheer intrest of VP. It would quite possible that i may also asked to leave after certain time when contract period will be over.
I have learned two lesson from this incedent:
1) Never disclose your cards to upper management unless you are not part of them.
2) Always create situation where you are needed most. As soon as you are no longer needed, you will be kicked out.
So In summary, lesson is, don't do good work unless you are not sure that you are going to get benefit of the work you have done!
That's why i hate to be in management.:)
Subscribe to:
Posts (Atom)