I was sad to see Linus choose the path of demagoguery and shout down opposing viewpoints. It's ironic that he used scientific theory as an example, because that isn't how it works at all. Authors of scientific theories welcome criticism because it allows them to work out kinks and strengthen their arguments. That's why papers are written in scientific journals for peer review.
This is how software design methodology is supposed to work as well. Yes, a "spec" is an approximation of reality, but as that reality is discovered during the development process, the spec should be changed to reflect it. Unfortunately, refining the specification often means moving back deadlines, which affects promises made by business leaders. That's the reality of designing software.
I think Linus is frustrated with the dysfunction often associated with the process and has identified his frustration with the process itself. It's absurd to say that software should be written by the seat of the pants. The failure of that model is what has caused software design methodologies to be created in the first place. Linus should know better than that.
Slashdot Mirror
That way we could know if it was the spicy thai kind.
My mistake.
Card hasn't even seen The Matrix.
c ard/index.html
http://edition.cnn.com/books/dialogue/9908/orson.
Question: What do you think of the movie The Matrix?
Orson Card: Haven't seen The Matrix.
Alrighty then.
I was sad to see Linus choose the path of demagoguery and shout down opposing viewpoints. It's ironic that he used scientific theory as an example, because that isn't how it works at all. Authors of scientific theories welcome criticism because it allows them to work out kinks and strengthen their arguments. That's why papers are written in scientific journals for peer review. This is how software design methodology is supposed to work as well. Yes, a "spec" is an approximation of reality, but as that reality is discovered during the development process, the spec should be changed to reflect it. Unfortunately, refining the specification often means moving back deadlines, which affects promises made by business leaders. That's the reality of designing software. I think Linus is frustrated with the dysfunction often associated with the process and has identified his frustration with the process itself. It's absurd to say that software should be written by the seat of the pants. The failure of that model is what has caused software design methodologies to be created in the first place. Linus should know better than that.