1. All software breaks, so let's avoid failure by not even trying.
2. Constraining the user to simple tools, because the user is an idiot.
3. There is only one correct way to do something, and it's mine. Coming up with one mediocre way to do things is already a great accomplishment; thinking about design tradeoffs is unthinkable. YOLO!
4. The dependencies of a system are not fun, so they are your responsibility. Good luck.
5. Standards are a source of inspiration, idiots (see #2 above) aren't going to run into interoperability problems, missing features, and other consequences of implementing only the "simple" parts of the standard.
The cproc missing features list is a brief but very insightful example of this way of thinking (I mean, this way of not thinking).
Comments
Simplistic software manifesto.
1. All software breaks, so let's avoid failure by not even trying.
2. Constraining the user to simple tools, because the user is an idiot.
3. There is only one correct way to do something, and it's mine. Coming up with one mediocre way to do things is already a great accomplishment; thinking about design tradeoffs is unthinkable. YOLO!
4. The dependencies of a system are not fun, so they are your responsibility. Good luck.
5. Standards are a source of inspiration, idiots (see #2 above) aren't going to run into interoperability problems, missing features, and other consequences of implementing only the "simple" parts of the standard.
The cproc missing features list is a brief but very insightful example of this way of thinking (I mean, this way of not thinking).