Post History
This discussion was prompted by answers to this question. While the answers are good (basically, when designing for the medical field, either be or hire someone knowledgeable about the specific re...
Question
discussion
#2: Post edited
by
Sclrx
·
2023-08-22T15:40:09Z (about 1 year ago)
- This discussion was prompted by answers to [this question](https://electrical.codidact.com/posts/289472).
- While the answers are good (basically, when designing for the medical field, either be or hire someone knowledgeable about the specific requirements of that field), it is only relevant if the question was asked by a professional (or wannabe professional). In this specific case, it is possible to design what the asker wants in a reasonably safe manner (I think).
- A lot of questions can be answered two ways :
- 1. "here is how we do it, the components/design blocks/standards/etc. that are used to achieve that"
- 2. "Here is the process, norms, certifications and documentation you need to be able to sell your device in the US/Europe/other."
- What bothers me is I think the original question is interesting and deserves a technical answer as well as a process/compliance one.
- * Should a good answer include both aspects?
* How do we treat dangerous questions, like "How to build a tesla coil?" or "how do I control a firework show from an arduino?"
- This discussion was prompted by answers to [this question](https://electrical.codidact.com/posts/289472).
- While the answers are good (basically, when designing for the medical field, either be or hire someone knowledgeable about the specific requirements of that field), it is only relevant if the question was asked by a professional (or wannabe professional). In this specific case, it is possible to design what the asker wants in a reasonably safe manner (I think).
- A lot of questions can be answered two ways :
- 1. "here is how we do it, the components/design blocks/standards/etc. that are used to achieve that"
- 2. "Here is the process, norms, certifications and documentation you need to be able to sell your device in the US/Europe/other."
- What bothers me is I think the original question is interesting and deserves a technical answer as well as a process/compliance one.
- * Should a good answer include both aspects?
- * Should we use "hobbyist" and "professional" tags to specify what kind of answer we are looking for?
- * Should we simply write more specific questions? ("What are the requirements when designing a device to be used in the medical field?" vs "I am hacking together an EMG in my college dorm, what should I pay attention to?"
- * 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?"
#1: Initial revision
by
Sclrx
·
2023-08-22T15:33:47Z (about 1 year ago)
Professional vs Hobbyist advice and potentially dangerous projects
This discussion was prompted by answers to [this question](https://electrical.codidact.com/posts/289472). While the answers are good (basically, when designing for the medical field, either be or hire someone knowledgeable about the specific requirements of that field), it is only relevant if the question was asked by a professional (or wannabe professional). In this specific case, it is possible to design what the asker wants in a reasonably safe manner (I think). A lot of questions can be answered two ways : 1. "here is how we do it, the components/design blocks/standards/etc. that are used to achieve that" 2. "Here is the process, norms, certifications and documentation you need to be able to sell your device in the US/Europe/other." What bothers me is I think the original question is interesting and deserves a technical answer as well as a process/compliance one. * Should a good answer include both aspects? * How do we treat dangerous questions, like "How to build a tesla coil?" or "how do I control a firework show from an arduino?"