Be Relentlessly Resourceful
I'm curious about contextual dependence in this...<p>For example, I can often be relentlessly resourceful in technical matters.  If an approach doesn't work, then there's some other combination of code that may get us there, it just won't be as easy or elegant.  But then we can usually simplify it after the fact to make it reasonably maintainable.<p>But when it comes to social matters, I'm far more likely to just give up than to keep pushing people or trying different approaches.  A lot of that is simply because I know that code has no feelings: I won't be burning any bridges because I think that function definition deserves to die.  But it's hard to tell when you've pushed a person too far, or when they'll get offended because you went behind their back, and if that'll bite you later.<p>Is there a way to apply resourcefulness in one situation to another, and basically "cross-train" to become more persistent in different domains?