4 ms·
I'm not against offering to work on the problem in exchange for money. I'm against outright responding to a feature request with an estimate. If you don't want
by dictum 9y ago
I'm not against offering to work on the problem in exchange for money. I'm against outright responding to a feature request with an estimate.
If you don't want to work on the feature (i.e. you're uninterested), it's better to be honest about it.
If you do want to work on it, but your time would be better spent on anything else, and you're willing to work on it for money, first ask if the requester is interested in paying for it and then give your estimate.
The difference between a feature request and a client approaching a freelancer/company is that in the latter case, the other party initiates the conversation with a clear expectation of paying — they only have to decide if they like the terms and price.
- deleted 9y ago[deleted]
- wolfgke 9y ago> If you don't want to work on the feature (i.e. you're uninterested), it's better to be honest about it. Being uninterested to do it for free: Yes. But when I am interested to do it for money, giving an upfront estimate based on the hourly rate is the most honest way imaginable to me.