Tai Hang 3: The early product technology selection too tangled
14 or 152 days of May this year, I went to the Beijing International Convention Center for the 2nd session of the PHP Global Developers Conference as a translator for PHP founder Rasmus. Although I have confidence in my own English, but when I learned that Rasmus origin is Europe, but also worry about this friend's accent is too heavy, I do not understand, so in advance in the online search some of his information, see Listen, a little understanding.
In the conference's promotional copy 2 , I saw Rasmus's introduction:
The founder of the programming language PHP, wrote the first two versions of PHP, and participated in the development of a subsequent version of PHP. From September 2002 to November 6, 2009, he worked as an infrastructure architect at Yahoo! Corporation. 2010, joined WePay Company to help develop its API. Since 2011, he has been an entrepreneur consultant .
Because I happen to be in the business, so on his "entrepreneurial consultant" role is more curious, want to find the opportunity to consult Rasmus, in the entrepreneurial aspects have any experience to share.
Rasmus's speech at 15th, about 2 o'clock in the afternoon, he 12:30 to the venue to debug equipment, adjust the speech, very serious. At this time, most people go to dinner, there are not many people in the hall, I was on that side to give him a dozen hands, while chatting with him for a while. So I asked him (to the effect): "As a start-up consultant, you should give many start-up companies have consulted." Many of the engineers at the conference also have the idea of starting a business, do you have any suggestions for us? ”
"I've seen a lot of startups that have struggled with the initial technology selection, whether it's PHP, Java, or go," he said. They devote too much time and effort to the choice of tools, but ignore the problems that should be solved with tools. This is downright the cart before the horse, is wrong, you should avoid. ”
http://iosre.com/t/topic/4205
They devote too much time and energy to the choice of tools, but ignore the problems that should be solved by tools.