Are you going to also follow his advice and hire two or three different people to work on the the first bit of the project?
I think it's an interesting idea; it acknowledges how likely it is for a software project to fail, or to at least be mediocre. I've always wondered whether large companies might be able to do well with several teams working on the same projects, and a process where one team's code is periodically selected to form the basis of the next version, then everyone else starts from there.
Comments
I missed the how to hire article so I'm glad you included it. (For anyone else who did, here's the HN discussion: http://news.ycombinator.com/item?id=1445500 )
Are you going to also follow his advice and hire two or three different people to work on the the first bit of the project?
I think it's an interesting idea; it acknowledges how likely it is for a software project to fail, or to at least be mediocre. I've always wondered whether large companies might be able to do well with several teams working on the same projects, and a process where one team's code is periodically selected to form the basis of the next version, then everyone else starts from there.