Recognizing and accepting what we don't know about professional software production

What if there are claims we cannot evaluate nowadays because there is no way to prove if they are correct or not?

What if is hard to distinguish between mainstream ideas that everyone like from what really work in practice?

 What if orthodoxy is used as a weapon to oppose disagreement and dissent in support of someone authoritativeness?

What if for some problems we have to be highly intelligent and well informed just to be undecided about them?

What if we recognize and accept what we really known about professional software production and what we do not?

See also:
- Computer Science Is Not a Science, Communications of the ACM, Vol. 56 No. 1, Pages 8-9
- Two Solitudes Illustrated, about IT industry and academia
- Why you should not be an Agilist
- Many ways of looking at Software development, from software cults to software fashion
- When diversity, dissent and responsibility lack

Print | posted @ sabato 27 ottobre 2012 19:52

Comments have been closed on this topic.