Each routine you read turns out to be pretty much what you expected. You can call it beautiful code when the code also makes it look like the language was made for the problem.

When I was at Tek, I was frustrated that computer hardware was being improved faster than computer software. I wanted to invent some software that was completely different, that would grow and change as it was used. That's how wiki came about.

The shortest path to exceeding expectations doesn't generally pass through meeting expectations.

Global collaboration is something that Wiki mastered in a small way and here we can master it in a big way.

When a manager asks for hard data, that's usually just his way of saying no.

When you get in situations where you cannot afford to make a mistake, it's very hard to do the right thing. So if you're trying to do the right thing, the right thing might be to eliminate the cost of making a mistake rather than try to guess what's right.

What's the simplest thing that could possibly work?