Software Engineering, Not Computer Science [2004]
stevemcconnell.com1 pointsby tst0 comments
------------------------------------------------------------------------------
support | Coef. Std. Err. z P>|z| [95% Conf. Interval]
-------------+----------------------------------------------------------------
age | .0258551 .0358136 0.72 0.470 -.0443382 .0960485
is_democrat | -1.252883 .6243361 -2.01 0.045 -2.476559 -.0292067
seniority | -.0262688 .0381962 -0.69 0.492 -.101132 .0485943
quota_ent | 5.839435 1.447732 4.03 0.000 3.001933 8.676938
_cons | -1.968467 2.01512 -0.98 0.329 -5.918029 1.981096
------------------------------------------------------------------------------
The AUC is 0.8089 which is quite okay. Furthermore, it would be interesting to test whether location is a significant factor.
The biggest problem with checklists, flow charts and software (one older example is MYCIN [1]) is adaption. If the medical practitioners don't want the systems they are going to fail. He also writes a lot about that in the book. He tried to introduce it into hospitals but the professionals often ignored the lists or just checked the boxes without actually checking the condition.
I personally imagine that a practitioner with a good system works the best or like Frederick P. Brooks said [2]:
> If indeed our objective is to build computer systems that solve very challenging problems, my thesis is that IA > AI that is, that intelligence amplifying systems can, at any given level of available systems technology, beat AI systems. That is, a machine and a mind can beat a mind-imitating machine working by itself.
[0]: http://en.wikipedia.org/wiki/The_Checklist_Manifesto
[1]: http://en.wikipedia.org/wiki/Mycin
[2]: http://www.cs.unc.edu/~brooks/Toolsmith-CACM.pdf