Post History

Software design in itself has always been on-topic, as per https://software.codidact.com/help/on-topic. 

As for system design for a given purpose, I think it is fine within reason. Contrary to popular belief, a certain degree of domain expertise or at least insight is always necessary when writing computer programs. It isn't really possible to only work with abstract programming in a vacuum, without a clue about the intended use and the end product. You _could_ do that, but you will be designing bad, dysfunctional products.

---

I think the key is:

**The focus of the question has to be about software design/programming, not about the domain-specific parts.**

So a good question might go:

"I'm designing an automatic pony-feeder system. Here is my OO design and the list of use-cases `<details>`. Does the design make sense and what languages and platforms may be suitable for the problem? I'm thinking that MyLittlePonySQL might be a suitable DBMS because `<reasons>`, any thoughts about that?" 

And a bad question:

"I'm designing an automatic pony-feeder system. I'm looking for feedback of what kinds of food it needs to handle and how much ponies eat per day, depending on age. If anyone knows of a pony feeding project on Github, I'd like to hear about that too."

That's nothing about programming, all about the domain expertise and shouldn't be asked here, but on some horse site. Furthermore, asking where to find off-site resources is generally unsuitable for Q&A sites.

---

However, the examples you give (as well as my pony one) are mostly regarding embedded systems design, so they don't belong here for that reason, since the consensus so far is that we should try to keep such questions on electrical.codidact.com. Big picture, domain-specific design questions have been mostly well-received there in the past ([example](https://electrical.codidact.com/posts/288641), [example](https://electrical.codidact.com/posts/285186)).