Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Meta

Post History

66%
+4 −1
Meta Professional vs Hobbyist advice and potentially dangerous projects

the original question is interesting and deserves a technical answer So go write one. That's your call, just like it's mine not to. We are all volunteers here, and are therefore never obligated ...

posted 1y ago by Olin Lathrop‭

Answer
#1: Initial revision by user avatar Olin Lathrop‭ · 2023-08-22T21:15:36Z (over 1 year ago)
<blockquote>the original question is interesting and deserves a technical answer</blockquote>

So go write one.  That's your call, just like it's mine not to.

We are all volunteers here, and are therefore never obligated to answer anything.  I didn't answer with technical details because:<ol>

<li>I don't know all the specs for medical devices off the top of my head.  I didn't feel like looking them up for the OP.

<li>My impression was that the OP is in way over his head and has no idea how complicated and rigorous the process is.  He needs a reality check and isn't ready for technical specs.

<li>Even if I knew the specs and they were easy to spell out in an answer here (definitely not the case), I still wouldn't have given them.  I got the feeling that if someone just gave the OP the specs, he'd run off and try designing the device and ignore all that annoying process stuff everyone was on about.  Nothing useful would come of that, neither for the OP nor the public.

</ol>

<blockquote>Should a good answer include both aspects?</blockquote>

Maybe, depending on the situation, but then again the answerers are volunteer and get to answer whatever part (including none) of any question they feel like.

You can leave a comment and/or downvote an answer you feel is bad.  However, I wouldn't do that just because you think more could have been said.  That's probably true of all answers here.  I would judge an answer on the quality of what was said, not what was left unsaid.  The only exception would be if the missing information is crucial to what was provided, to the point where the answer without it is misleading, thereby providing negative overall value to the OP and the site.

<blockquote>How do we treat potentially dangerous questions, like "How to build a tesla coil?" or "how do I control a firework show from an arduino?"</blockquote>

In whatever way you want to.  If you feel like jumping into the technical details, that's fine.  If you only want to warn of the potential dangers, that's fine.  If you don't want to answer at all, that's fine.  And, you don't owe anyone an explanation for any of the above.

In general, we don't want to tell others what parts of questions they must address.  There are a few exceptions, like don't ever answer a homework problem directly.  But overall, we don't want to tell the volunteers what they must do.