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

How to deal with design review questions?

+2
−0

A while back someone suggested that we added a section for reviews to the site - How about a new section for code reviews? From that meta thread we gathered that:

  • There seems to be community consensus that code review is perfectly fine and on-topic for this site, given that the topic is about microcontroller/DSP firmware, HDL code or similar embedded systems software.
  • It was proposed that reviews should not be limited to code but to all forms of electrical engineering. Things like for example review of schematics, PCB layout/stack-up and EMC design.
  • There was no consensus about adding a separate category for this. Some 2 years later, we can conclude that review questions are rare and the few ones we have are almost always about schematics/design. There aren't many questions about firmware at all.

I'd like to encourage more questions like this - design reviews is a healthy process and excellent for learning and sharing everything from the fundamentals to handy tips & tricks, as well as for spotting errors that you as a designer are blind to yourself.

Since the tags are going through a bit of an overhaul right now, perhaps we should simply add a tag design-review with a tag description outlining what we expect from review questions? And in case this would turn out popular we can always create a category for it later.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

Visibility (6 comments)

1 answer

+1
−0

I agree with this approach. Categories should only be created when they are expected to have reasonable traffic.

A category with only chirping crickets is an anti-advertisement. Take a look at the Photography and Outdoors sites. They have lots of nearly unused categories, which I think makes those sites look even more dead than they already are.

Your idea of a special tag seems like a good solution for now. If by some miracle we get flooded with design review questions, it will be easy to find the existing ones so that they can be moved to a new category.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

0 comment threads

Sign up to answer this question »