Go Down

Topic: why is it so difficult to get a response? (Read 3983 times) previous topic - next topic

JimboZA

You need to remember that this isn't a manufacturer's help desk- it's an enthusiasts' forum.

Sometimes you get a zillion replies, sometimes you get 5, or 0. It depends on so many things, not least of which is does anybody actually have the knowledge to answer? If they do have, well sometimes they just don't see your thread; didn't log on that day, didn't have time, meant to get back to it after some testing, and yes, just took the dog for a walk instead and didn't share their knowledge.

You'll see threads where there are replies over days with one member painstakingly walking someone through a complicated solution, advising on circuit, components and code: in a case like that the opening post clearly grabbed someone's attention, and it's awesome when that happens. But sometimes, it's just tough shit that nobody latched onto a thread with a solution.

Still keen to hear what my compatriot actually means by this:

it's all posts but little replies
Johannesburg hams call me: ZS6JMB on Highveld rep 145.7875 (-600 & 88.5 tone)
Dr Perry Cox: "Help me to help you, help me to help you...."
Your answer may already be here: https://forum.arduino.cc/index.php?topic=384198.0

TomGeorge

Hi,

Quote
it's all posts but little replies
If each post has at least 2 replies, that's twice as many replies as posts, isn't it?

Mathematically;

posts << replies

Tom... :)
Everything runs on smoke, let the smoke out, it stops running....

nickgammon

Why is it so hard to get an answer on this forum? I mean damn. I posted twice asking about an issue I had interfacing a ps2 controller.
OK, I had a look at one of those posts. (http://forum.arduino.cc/index.php?topic=317601)

No code posted. No wiring. And the output was a screenshot, when copy and paste of the text would have been more helpful.

After putting a lot of trouble into making the post about "how to use this forum" ( http://forum.arduino.cc/index.php?topic=148850.0) sometimes I just can't be bothered going through the "here we go again, like extracting teeth" ... what code did you use? what wiring did you use? And I move onto another post.

Now let's check your other post about it (basically a cross-post).  In that you say:

Quote
I've got photos and more info that I can post.
Why be shy? Post it. Post your schematic (the photo doesn't tell a lot), and your code, and the actual results you get.
Please post technical questions on the forum, not by personal message. Thanks!

More info: http://www.gammon.com.au/electronics

nickgammon

#18
Apr 25, 2015, 09:08 am Last Edit: Apr 25, 2015, 09:09 am by Nick Gammon
Oh, yes: Google: ps2 controller arduino

Quote
About 75,300 results (0.30 seconds)
You might want to mention which of those you tried, and in what way those 75,000+ results did not work for you.
Please post technical questions on the forum, not by personal message. Thanks!

More info: http://www.gammon.com.au/electronics

JimboZA

#19
Apr 25, 2015, 09:11 am Last Edit: Apr 25, 2015, 09:12 am by JimboZA
Quote
No code posted. No wiring. And the output was a screenshot, when copy and paste of the text would have been more helpful.
When you put it like that, Nick, not surprising the OP had no joy.
Johannesburg hams call me: ZS6JMB on Highveld rep 145.7875 (-600 & 88.5 tone)
Dr Perry Cox: "Help me to help you, help me to help you...."
Your answer may already be here: https://forum.arduino.cc/index.php?topic=384198.0

nickgammon

Interestingly, this thread got quite a few responses, quite quickly. So, people do respond to an interesting topic. Your job? Make the topic interesting.
Please post technical questions on the forum, not by personal message. Thanks!

More info: http://www.gammon.com.au/electronics

nickgammon

Quote
I posted twice asking about an issue I had interfacing a ps2 controller.
The other thing here is, you were lucky you didn't get reported for cross-posting. And once I've merged cross-posted threads together, I am personally less likely to "reward" the cross-poster by doing a prompt reply.
Please post technical questions on the forum, not by personal message. Thanks!

More info: http://www.gammon.com.au/electronics

JimboZA

#22
Apr 25, 2015, 09:17 am Last Edit: Apr 26, 2015, 08:09 am by JimboZA
Interestingly, this thread got quite a few responses, quite quickly. So, people do respond to an interesting topic. Your job? Make the topic interesting.
Took the words out of my mouth.....

And you only need to look at the phenomenal individual post counts up in the 10-20-30k, not to mention PaulS up in the mid-50s, to realise that people do respond. But they have to read the thread in the first place and then have something to say....
Johannesburg hams call me: ZS6JMB on Highveld rep 145.7875 (-600 & 88.5 tone)
Dr Perry Cox: "Help me to help you, help me to help you...."
Your answer may already be here: https://forum.arduino.cc/index.php?topic=384198.0

GoForSmoke

Extraordinary questions require extraordinary work and knowledge covered already as well as links to docs and then getting answered may hinge in "do I want to get involved in this?" and "can I help without getting involved?".

When I see "I'm totally new to this and want to do pro work right away", I either advise "learn the basics first" or just leave. If they feel touchy about that, just wait till they spend a few hours with a compiler, actually doing the work instead of asking about it and demanding examples.

Don't like being told you're wrong? Meet the compiler! Argue with it!
1) http://gammon.com.au/blink  <-- tasking Arduino 1-2-3
2) http://gammon.com.au/serial <-- techniques howto
3) http://gammon.com.au/interrupts
Your sketch can sense ongoing process events in time.
Your sketch can make events to control it over time.

Go Up