Tim's post is very interesting, but in my opinion should be changed in "Never reject a feature request", which means that every time a feature is requested, it should not be dubbed as "crack", but neither accepted as is: we should try hard to understand which problem and use case drives that request and try to come up with a solution to the underlying problem. The solution may or may not be the exact request proposed by the reporter: often who identifies a problem is not the best suited person to find the solution.

After all it's Linus himself that often says that "the main job of a free software maintainer is to say no"