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

77%
+5 −0
Meta How about a new section for code reviews?

Regarding scope of embedded systems/firmware When we released Software Development, I made a push to make all forms of embedded systems programming off-topic and re-direct such to this site. The ...

posted 3y ago by Lundin‭  ·  edited 3y ago by Lundin‭

Answer
#2: Post edited by user avatar Lundin‭ · 2021-01-26T07:59:48Z (about 3 years ago)
  • **Regarding scope of embedded systems/firmware**
  • When we released Software Development, I made a push to make all forms of embedded systems programming off-topic and re-direct such to this site.
  • The reason for this is is my experience from the "embedded" tag over at SO, where I'm one of the top users and pretty much the only one that has been consistently moderating that tag over the years. That tag attracts a whole lot of bad or off-topic questions.
  • Embedded systems trouble-shooting or review questions asked at a pure software site almost always end up in the borderland between software and hardware. It is very common that you don't know if the reason for the problem is located in software or hardware. And then it is not sufficient just to view the source code to find the problem, you'll need datasheets and schematics too.
  • Also, if the problem happens to be the software, the question is on-topic for the programming site. But if the problem was hardware, then suddenly it is off-topic.
  • So these kind of questions were always best to ask at the Electrical Engineering sites, where firmware development (microcontrollers, HDL, PLC etc) is on-topic.
  • ---
  • **Regarding reviews**
  • This means that code review questions of firmware are also best asked at the Electrical Engineering site.
  • I've been participating in SE's Code Review site too, and whenever embedded systems questions pop up there, you tend to get confused PC programmers chiming in, coming up with advise that ranges from mildly useful to horribly wrong.
  • Generally, I think all forms of design review of electronics should be on-topic here. Schematics, component choice, PCB layout, real-time requirements, source code.
  • (Take for example someone asking for a review of their switch debouncing. They are using RC low pass filters as well as a software filter. How do you review that overall design without viewing schematics + code both?)
  • So if we are to make a new category, it should perhaps be named ***Design reviews*** and not just restricted to source code, but to any form of design reviews. I'd love to see more design reviews of schematics and layouts on this site too.
  • **Regarding scope of embedded systems/firmware**
  • When we released Software Development, I made a push to make all forms of embedded systems programming off-topic and re-direct such to this site.
  • The reason for this is is my experience from the "embedded" tag over at SO, where I'm one of the top users and pretty much the only one that has been consistently moderating that tag over the years. That tag attracts a whole lot of bad or off-topic questions.
  • Embedded systems trouble-shooting or review questions asked at a pure software site almost always end up in the borderland between software and hardware. It is very common that you don't know if the reason for the problem is located in software or hardware. And then it is not sufficient just to view the source code to find the problem, you'll need datasheets and schematics too. Quite often the problem is related to how a certain data bus is used.
  • Also, if the problem happens to be the software, the question is on-topic for the programming site. But if the problem was hardware, then suddenly it is off-topic.
  • So these kind of questions were always best to ask at the Electrical Engineering sites, where firmware development (microcontrollers, HDL, PLC etc) is on-topic.
  • ---
  • **Regarding reviews**
  • This means that code review questions of firmware are also best asked at the Electrical Engineering site.
  • I've been participating in SE's Code Review site too, and whenever embedded systems questions pop up there, you tend to get confused PC programmers chiming in, coming up with advise that ranges from mildly useful to horribly wrong.
  • Generally, I think all forms of design review of electronics should be on-topic here. Schematics, component choice, PCB layout, real-time requirements, source code.
  • (Take for example someone asking for a review of their switch debouncing. They are using RC low pass filters as well as a software filter. How do you review that overall design without viewing schematics + code both?)
  • So if we are to make a new category, it should perhaps be named ***Design reviews*** and not just restricted to source code, but to any form of design reviews. I'd love to see more design reviews of schematics and layouts on this site too.
#1: Initial revision by user avatar Lundin‭ · 2021-01-26T07:58:04Z (about 3 years ago)
**Regarding scope of embedded systems/firmware**

When we released Software Development, I made a push to make all forms of embedded systems programming off-topic and re-direct such to this site.

The reason for this is is my experience from the "embedded" tag over at SO, where I'm one of the top users and pretty much the only one that has been consistently moderating that tag over the years. That tag attracts a whole lot of bad or off-topic questions.

Embedded systems trouble-shooting or review questions asked at a pure software site almost always end up in the borderland between software and hardware. It is very common that you don't know if the reason for the problem is located in software or hardware. And then it is not sufficient just to view the source code to find the problem, you'll need datasheets and schematics too. 

Also, if the problem happens to be the software, the question is on-topic for the programming site. But if the problem was hardware, then suddenly it is off-topic. 

So these kind of questions were always best to ask at the Electrical Engineering sites, where firmware development (microcontrollers, HDL, PLC etc) is on-topic.

---

**Regarding reviews**

This means that code review questions of firmware are also best asked at the Electrical Engineering site. 

I've been participating in SE's Code Review site too, and whenever embedded systems questions pop up there, you tend to get confused PC programmers chiming in, coming up with advise that ranges from mildly useful to horribly wrong. 

Generally, I think all forms of design review of electronics should be on-topic here. Schematics, component choice, PCB layout, real-time requirements, source code.

(Take for example someone asking for a review of their switch debouncing. They are using RC low pass filters as well as a software filter. How do you review that overall design without viewing schematics + code both?)

So if we are to make a new category, it should perhaps be named ***Design reviews*** and not just restricted to source code, but to any form of design reviews. I'd love to see more design reviews of schematics and layouts on this site too.