When people work code they can often see things I set out to do that they wouldn't notice otherwise. And there are no obligations to say, "Ward you're brilliant," but sometimes they say, "Ward you're brilliant." And that strokes my ego. Pride of ownership? You bet.
Ward Cunningham
» Ward Cunningham - all quotes »
"It was very, very hard work organizing that Wall concert but everyone was fabulous to work with - Bryan Adams, Van Morrison, Cyndi Lauper, bloody brilliant. All brilliant. Except for Sinead O'Connor... She doesn't understand anything. She's just a silly little girl. You can't just lie in the corner and shave your bloody head and stick it up your arse and occasionally pull it out to go (_"brogue"_) 'Oh, I tink this is wrong and dat is wrong' and burst into tears."
Roger Waters
In the months before I made wiki, we had been having an argument. I think Kent Beck and I were on one side. People who had a lot of faith in the prevailing dogma of software engineering were on the other side. We said, "Collective code ownership is good." They said, "That's ridiculous. You'll never get responsibility. You'll never get quality if you don't have responsibility. And the only way you'll get responsibility is ownership. You have to pin the bugs back on somebody if you want them to ever rise above producing bugs." And I said, "Well that's wrong."
Ward Cunningham
Often as you move comments around and have similar comments adjacent to each other, you find that half of the words can be cut out. Because a sentence says it all if the sentence is in just the right place. On Ward's wiki, the process has been called "refactoring," which is what we call the process in software. Ward's wiki is about software and it has software people on it, so they call it refactoring. Anyplace else it would probably be called editing. So on Ward's wiki, refactoring is an ongoing process. The assumption is that when something turns out to not be ideal, it will be refactored again. Everything is subject to refactoring.
Ward Cunningham
Why don't we write code that just works? Or absent a "just works" set of patches, why don't we revert to code that has years of testing? This kind of "I broke things, so now I will jiggle things randomly until they unbreak" is not acceptable. [...] Don't just make random changes. There really are only two acceptable models of development: "think and analyze" or "years and years of testing on thousands of machines". Those two really do work.
Linus Torvalds
"The only trend I do not like in rap right now is the message rap. I consider the message rap the equivalent of what strings were to rock 'n' roll in the late '50s - a capitulation to the adult norm who can't accept the music on its own terms. The people who considered "Sixty Minute Man" by Billy Ward and the , "Annie Had a Baby" - as the pinnacles of '50s R&B now are super uptight over the - in quotes - hotel/motel lyrics of rap. Rap is definitely as true to the essence of rock 'n roll as anything that's out there today."
Aaron Fuchs
Cunningham, Ward
Cunninghame-Grahame of Gartmore, Robert
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
T
U
V
W
X
Y
Z