&gt; You ask a complex question and they ask you why you&#x27;re doing it.<p>As someone on the other side of those questions, perhaps I can explain.<p>Very often, people unfamiliar with a subject area ask questions about solutions, instead of asking about problems.  They&#x27;ve done a bit of googling, and have a partial solution.  But the solution doesn&#x27;t work, so they ask &quot;how can I fix this solution.&quot;<p>To someone familiar with the problem space, the question is often nonsensical.  It&#x27;s based on false assumptions about how the API &#x2F; system works.  So the question is largely un-answerable.<p>The only possible response, then, is &quot;Don&#x27;t talk about the solution.  Talk about the problem.  What goal are you trying to accomplish?  Maybe there&#x27;s a different solution which can help you reach that goal.&quot;<p>This response can be seen as obtuse and unhelpful by the questioner.  But it&#x27;s often the only possible response, given the incorrect assumptions.<p>e.g. Q: How do I get diesel into my gas car?  The nozzle just doesn&#x27;t fit!<p>A: Why are you trying to do that?<p>Q: Stop being annoying, and just help me!<p>A: No, really... why are you trying to do that?<p>(after some back and forth)<p>Q: My car is in front of the diesel pump, and the hose from the gas pump won&#x27;t reach.<p>A: Well... move your car.<p>It&#x27;s not always that simple, but the back &amp; forth is similar.  It&#x27;s hard work convincing people that their assumptions are wrong, and that they have to re-visit their assumptions, and re-do all of their previous work.