Quotes

Tim Berners-Lee on Web 2.0

LANINGHAM (interviewer): You know, with Web 2.0, a common explanation out there is Web 1.0 was about connecting computers and making information available; and Web 2 is about connecting people and facilitating new kinds of collaboration. Is that how you see Web 2.0?

BERNERS-LEE: Totally not. Web 1.0 was all about connecting people. It was an interactive space, and I think Web 2.0 is of course a piece of jargon, nobody even knows what it means. If Web 2.0 for you is blogs and wikis, then that is people to people. But that was what the Web was supposed to be all along.
http://www-128.ibm.com/developerworks/podcast/dwi/cm-int082206.txt

Kent Beck on software

Listening, Designing, Coding, Testing – That’s all there is to software. Anyone who tells you different is selling something

Kent Beck on requirements

Software development has been steered wrong by the word ‘requirement,’ defined in the dictionary as something mandatory or obligatory. The word carries a connotation of absolutism and permanence – inhibitors to embracing change. And, the word ‘requirement’ is just plain wrong.

From: 2nd edition of Extreme Programming Explained

Tim Bray on SOA

“What do you think we should do about SOA?” Which weirdly, nobody had asked me before, and I could find only one answer: “Don’t do anything. ‘SOA’ may have meant something once but it’s just vendor bullshit now.”

Tim Bray
http://www.tbray.org/ongoing/When/200x/2006/04/17/SOA-or-not

Martin Fowler on comprehensive diagrams

A common problem with the common use of diagrams is that people try to make them comprehensive. The code is the best source of comprehensive information, as the code is the easiest thing to keep in sync with the code. For diagrams comprehensiveness is the enemy of comprehensibility.

From: http://www.martinfowler.com/articles/designDead.html

Fred Brooks on Judgement and experience

Good judgement is the result of experience. Experience is the result of bad judgement.