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.

And then there are difficulties. Computers are famous for difficulties. A difficulty is just a blockage from progress. You have to try a lot of things. When you finally find what works, it doesn't tell you a thing. It won't be the same tomorrow. Getting the computer to work is so often dealing with difficulties.

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

What is simplicity? Simplicity is the shortest path to a solution.

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

Over and over, people try to design systems that make tomorrow's work easy. But when tomorrow comes it turns out they didn't quite understand tomorrow's work, and they actually made it harder.

I can't tell you how much time is spent worrying about decisions that don't matter. To just be able to make a decision and see what happens is tremendously empowering, but that means you have to set up the situation such that when something does go wrong, you can fix it.

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

The best way to get the right answer on the Internet is not to ask a question, it's to post the wrong answer.

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.

Why have a locked wiki when you can instead just post static Web pages?

A wiki works best where you're trying to answer a question that you can't easily pose, where there's not a natural structure that's known in advance to what you need to know.

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.

I don't claim to be a methodologist, but I act like one only because I do methodology to protect myself from crazy methodologists.

There's been an awful lot of discussion about what is or isn't simple, and people have gotten a pretty sophisticated notion of simplicity, but I'm not sure it has helped.

What's the simplest thing that could possibly work?