Quote

The cost of adding a feature isn't just the time it takes to code it. The cost also includes the addition of an obstacle to future expansion. The trick is to pick the features that don't fight each other.

When I was a student and rushing to finish a project, my gut instinct was usually to keep adding all kinds of features. It's a way of papering over the fact that you haven't quite nailed your concept yet.

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

And, I think that is actually appropriate because I'm really not the world's best programmer, I think it's a good thing that I'm not touching the code.

All of our code is open source, so it can be used for other projects.

You shouldn't restrict peoples' freedom on what they can and cannot do with code.

If you make an error, use it as a stepping stone to a new idea you might not have otherwise discovered.

I'm not saying we purposely introduced bugs or anything, but this is kind of a natural result of any complexities of software... that you can't fully test it.

I think complexity is mostly sort of crummy stuff that is there because it's too expensive to change the interface.