Discussions about the meaning of words, while sometimes fun, only rarely produce any useful results. Generally it is better to choose some precise definition in your context, and see what you can build from that / where does that take you.
This whole post is such a disguised discussion. He never picks a precise definition of "bug" or "feature request". If he did, it would be immediately obvious were each case lies - but then it would be also obvious the post is content-free...
At any case, it would be nice if there was some way of telling HackerNews "I don't want to see any posts coming from codinghorror"...
I think the point is exactly that these precise definitions should just be thrown out. The goal is to make something people want (or, at least, that they will pay for). Making distinctions about where bugs come from, who reports them, when in the cycle you found them, etc. are all part of most development processes, but they are masking the issue.
This whole post is such a disguised discussion. He never picks a precise definition of "bug" or "feature request". If he did, it would be immediately obvious were each case lies - but then it would be also obvious the post is content-free...
At any case, it would be nice if there was some way of telling HackerNews "I don't want to see any posts coming from codinghorror"...