Do the usual "How-to / Troubleshooting" restrictions apply to advice, best-practices, and tooling-recommendation questions?

I understand that Stack Overflow has fairly strict expectations for "How-to / Troubleshooting" questions—for example, they should be specific, show prior research, and, where applicable, include a minimal reproducible example.

Do those same restrictions apply to questions tagged advice, best-practices, or tooling-recommendation, or are these categories evaluated differently?

In particular, are questions like the following considered on topic?

  • What are the best practices for reviewing or integrating LLM-generated code?
  • Given specific requirements and a particular programming language, how should a program or system be designed?
  • Given a specific project and clearly stated requirements, which language is most suitable (for example, based on ecosystem, maintainability, or available features)?

If these types of questions are on topic:

  • What characteristics distinguish a good question in these categories from one that is considered too broad or primarily opinion-based?
  • Do they have different expectations from ordinary "How-to / Troubleshooting" questions?
  • What can I do when asking these kinds of questions to maximize the chances that they are well received rather than downvoted?

If the example questions are not on topic, where is the boundary? In other words, what would need to change for one of these example questions to become an acceptable Stack Overflow question?

添加评论
点赞收藏
点踩分享查看原文
评论
?
参与讨论