Mark Zuckerberg Quotes

Many people think that open source projects are sort of chaotic and and anarchistic. They think that developers randomly throw code at the code base and see what sticks.

There is no schedule. We are all volunteers, so we get it done when we get it done. Perl 5 still works fine, and we plan to take the right amount of time on Perl 6.

I work on OpenBSD fulltime, as the project leader. I set some directions, increase communication between the developers, and try to be involved in nearly every aspect of the base system.

After releasing Mono 1.0, we started work on a new edition of Mono that will be released later in the year.

Personally, I look forward to better tools for analyzing C++ source code.

Don't hurry your code. Make sure it works well and is well designed. Don't worry about timing.

Don't document bad code - rewrite it.

For WordPress to be world class, it needs to have a sustainable model.

In true open source development, there's lots of visibility all the way through the development process.

The Mozilla project is big in terms of lines of code and complexity.

There are two methods in software design. One is to make the program so simple, there are obviously no errors. The other is to make it so complicated, there are no obvious errors.

A new release of Plan 9 happened in June, and at about the same time a new release of the Inferno system, which began here, was announced by Vita Nuova.

Running the test suite like this allows us to catch problems when they are just introduced.

Most of the effort in the software business goes into the maintenance of code that already exists.

The beauty of open-source is that you can pick up right where someone left off and start right there.

What commercialism has brought into Linux has been the incentive to make a good distribution that is easy to use and that has all the packaging issues worked out.

My list of basic tools is a partial answer to the question about what has changed: Over the past few years, large numbers of programmers have come to depend on elaborate tools to interface code with systems facilities.

If you don't have the best product, you're not going to make it in open-source.

Cosmoe is nearing the stage where I would feel comfortable doing a preliminary release aimed at developers.

When I first got into technology I didn't really understand what open source was. Once I started writing software, I realized how important this would be.

No matter what, the way to learn to program is to write code and rewrite it and see it used and rewrite again. Reading other people's code is invaluable as well.

Early in my career, I was involved with engineer-led projects, where designers came in late in the game and were expected to put lipstick on an existing code base. This almost never works.

There are two main methodologies of open source development. There's the Apache model, which is design by committee - great for things like web servers. Then you have the benevolent dictator model. That's what Ubuntu is doing, with Mark Shuttleworth.

We have a very active testing community which people don't often think about when you have open source.

Developer testing is an important step towards accountability. It gives developers a way to demonstrate the quality of the software they produce.