When working on a project, don't solve problem that haven't arrived yet. It doesn't mean we don't know them, but we need to focus on the main problem first. The youtube guys didn't think of copyright videos before they started youtube. They were set to solve the web video sharing problem, and that's what they did. Stay focus; that's the reason we're working on the project in the first place. We're not working on a prject to look for future problem; we're working on a project to get the best solution to a main problem.
I have to disagree. There is a main goal, there are implications. We need to solve both of them to deliver good/great product or at least have proper precaution. Every now and then I remind myself about vista problem and how they got class action lawsuit.
I completely disagree. It's shoddy and inefficient to wait for a problem to arrive. Imagine if the guys at Google just sat around waiting for their server to kick the bucket before they fixed it; they'd be out of business.<p>Problems aren't mutually exclusive, I can fix more than one at once. If my server is bust, it doesn't matter if my ISP is cutting me off in a week, but if all it takes is a call to another ISP to get another connection before the deadline then I'm not going to turn 1 week of having a downed server into two weeks with no useable service.<p>Only solving problems as they arrive is the work of the mediocre, the good fix things before they arrive. By your own example, the YouTube guys -didn't- think of copyrighted videos and they got a $1 billion lawsuit! That isn't a smart thing to allow to happen, if precident gets set against YouTube in one single case, they're broke and gone because they didn't think ahead.
In general, I agree. But was there a huge demand for online video before YouTube launched? They were smart because they made it super simple, but they were a chicken chasing an egg in the beginning.