I've encountered that kind of resistance before as well. My normal technique for handling it is to have ruled it down to an issue with their component, but instead of hitting them directly with a "the problem is in your component" (preceived) frontal assault, I instead as them to verify the behavior of their component on the grounds of ruling it out as a part of the issue, while making it clear I am still examining other potential issues. This allows them to discover the issue, rather than having it be pointed out to them, and gives them the opportunity to save face. (It also allows for the removal of my foot from my mouth if instead I find there was something else I missed.)
(And I do agree with the appreciation of straight talk and lack of excuses. Your fault, my fault, nobody's fault-let's get the problem solved, and if anyone wants to talk about the dust motes in the eyes of others after having de-planked their own eyes when the current fire is over, they're welcome to.)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||