I really liked your comment and I'd like to add my own perspective, which is similar. My ideal as a developer is to project the same attitude to clients and bo

I really liked your comment and I'd like to add my own perspective, which is similar. My ideal as a developer is to project the same attitude to clients and bosses that I would like to have. It's not exactly my current attitude, but it would go something like this: If I know how to do something "Yes, I can do that, I've done that before and I'm familiar with the steps." If I don't "Yes, I can do that, I just need enough time to figure out how." Abstracted to general product marketing "Yes, we can meet your needs with our current product or figure out a way to do so at a cost of x to you" Any time that last statement turns out to be false in retrospect beyond some threshold (lets say 10% of the time), that's a sign of overselling. I guess the threshold is where some subjective fuzz comes into play. Likewise, the cost accuracy is important too (time also matters, but I'm rolling that into cost). Integrity is about avoiding such statements when impossible or when needs are extremely high. They can still be said with large costs (I can build you Google maps, but it would take over ten years). A lot of this derives from Patio11's comment collection. jasonshen: if you read this, thank you for the post. I really enjoyed it and admire the rejection therapy you've done in the past