1 |
Dirk Heinrichs wrote: |
2 |
|
3 |
>> heap. It's a classic example of "second system syndrome" as defined by |
4 |
>> "the mythical Man month". |
5 |
> |
6 |
> Errh, what? |
7 |
|
8 |
rtfb it was published in 1972, is still in print and the first five chapters |
9 |
are as relevant today as they were when it was first published. It explains why |
10 |
software projects fail. I think it's pretty sad when failings in an industry |
11 |
recognized 35 years ago are still happening today. |
12 |
|
13 |
Brooks says write one system to throw away because you are going to anyway. The |
14 |
first time you implement, you don't understand the problem and you frequently |
15 |
leave out functionality or implement things in a clumsy or incorrect way. This |
16 |
next implementation you, in theory, understand the problem and can do a better |
17 |
job which leads us to... |
18 |
|
19 |
second system syndrome. when you implement a system for the second time you |
20 |
think you have the problem fully understood, add lots of features and |
21 |
capabilities and end up with a disaster on your hands because you over estimated |
22 |
your capabilities. |
23 |
|
24 |
which is really Fred Brooks's way of saying write two system to throw away |
25 |
because you're going to anyway. |
26 |
|
27 |
a great example of this is Microsoft. They rarely get anything right until the |
28 |
third version (implementation). Other examples are easily found if you just look. |
29 |
|
30 |
> |
31 |
>> It's overly complicated, poorly documented, and |
32 |
>> has a terrible user interface that only a geek would even consider using. |
33 |
> |
34 |
> What's wrong with the excelent user guide on the project's site? Which of the |
35 |
> three UIs exactly do you think is horrible? |
36 |
|
37 |
could never get the containers nesting right. If the instructions on how to use |
38 |
an LVM can't be explained on a postcard, you don't understand how to communicate |
39 |
with your users or the implementation is really off. I spent lots of time on |
40 |
the mailing list talking to developers about various problems and a consistent |
41 |
problem was communicating the terminology to users. Simple things like how do |
42 |
you set up your physical disk was not documented well enough to be useful. |
43 |
|
44 |
the GUI tools did not lead you to a correct solution. It was just a bunch of |
45 |
menu items that you could choose a random. Hell, tinyca does a better job at |
46 |
guiding you in creating a small certificates hierarchy which is a task of |
47 |
similar complexity. |
48 |
|
49 |
-- |
50 |
Speech-recognition in use. It makes mistakes, I correct some. |
51 |
-- |
52 |
gentoo-user@g.o mailing list |