I have more experience on Stack Overflow than EESE, and I often come across questions here that strike me as too broad, but are either left open or even have upvotes. All of the following questions seem like "here are my requirements, design this for me" or "explain this massive complex topic" questions:
How do I design my very own ARM based processors?
How do I design a current transformer?
How to design blinking LEDs circuit using analog elements only?
How to design mutual inductor in proteus for wireless charging?
how to design a pattern detector state machine in vhdl
How design a circuit to control a switch?
How to program enc28j60??
How to Design a State Feedback Controller using an algorithm
I can think of a couple of explanations:
- EESE really does have a more relaxed definition of "too broad" than SO
- There aren't enough people with close-vote privileges for closures to keep pace with the incoming questions
- The standard of "too broad" is exactly the same and I'm misunderstanding why these particular questions don't meet it
- Some combination of all of the above
I've recently started reviewing first posts here (I've been doing it on SO for a while), and I want to make sure I'm understanding this site's expectations before I make a bunch of bad reviews.
I have read over this question and its answers: Should "how to design a project" questions always be put on hold as "too broad"?. The accepted (and most upvoted) answer makes perfect sense to me, but the example questions I've listed don't appear to meet that answer's criteria.
I would appreciate some commentary on the example questions I've listed. I would like to hear which of those questions I'm correctly and incorrectly judging as "too broad" and why.