What I hate is... in general, I only ask strange/oddball questions (because normal questions I GOOGLE first.). So on places like Stack Overflow and it pisses me off when even though I say "I understand I could do it X way, but I WANT TO DO IT Y WAY." I get the answer, "You shouldn't do it that way." They always reject the premise and suggest I should do it the "easy" way that everyone else is doing--even if that way doesn't actually satisfy my unique requirements or my specific learning application.
Like, "Is it possible to SECURELY run a web server on an old operating system like Windows 95 laptop." Almost everyone just whined about "use Linux instead" as-if drivers existed for my 30 year old laptop, or that modern flavors of Linux would easily run on my 8/16MB on RAM.
Another one is, using Powershell/WMI, I retrieve the per-process CPU/RAM/disk/IO usage statistics. The problem is, while CPU shows up, DISK USAGE is always reported to be zero. Even though, Task Manager in Windows 10 does report disk usage. (I thought Win7 might not report it but no, I still get it in Win10.) I tried to "help" them understand by coming up with a potential project "to graph per-process usage. This is for RESEARCH/LEARNING PURPOSES for powershell/wmi." And they go, "There are plenty of graphing utilities. Just use Process Explorer/Resource Monitor/etc." You idiots. That's not what I asked. And I even tried to spoonfeed them that it wasn't what I wanted. I wanted to know why WMI is broken.
My guess is, answering my specific questions require actual niche knowledge and most of the posters are only capable of providing general knowledge so they transform my question into one they can actually solve by assuming I'm stupid.
 So I wish there was a word or phrase that could easily say. I'M NOT STUPID. I believe I did my research. DO NOT ATTEMPT TO REDUCE MY PROBLEM. No Reductio Problema?</edit>
As for your specific issue. I'm not aware of any term, except simply saying (as nicely as possible) that the poster doesn't appear to be experienced enough to tackle this problem. Or, "your programming experience doesn't appear to meet the prerequisites to explain this properly."
Kind of reminds me of, "Is it Monday already?" (because of the huge influx of "I'm going to make a [project too complex for my ability or attention span]" project announcements we used to get here.) "All I need is a programmer, musician, artist, and idea guy... without pay. Any takers?"
One last thing. The Arduino and Raspberry Pi forums... woah man. Be careful there. They're FULL of people who talk out of their butts. I actually saw a legit post telling a guy that overclocking a raspberry pi (and HEAT) doesn't hurt it, but the FREQUENCY affects the "mean-time before failure" which reduces the amount of TIMES that the transistors CAN SWITCH before failing. Like they're some sort of mechanical relays falling apart. W. T. F.