It's time to choose a Question of the Week! The Question of the Week demonstrates what a good on-topic question looks like. Last week, we picked:

Suggest the next Question of the Week: just pick a good question from this search query and post the link as an answer. If you want to, add a short explanation why the suggested question is great.

Vote on suggestions to select the next Question of the Week. Ask yourself:

  1. Is this question firmly and unambiguously within the scope of Software Engineering?

  2. Is this an interesting and well-written question?

  3. Would I like to see more questions like that?

The next QotW will be the suggestion with the highest score by next Sunday. If you have doubts about a suggestion, you can discuss it in the comments.

Vote for this meta question if you like the Question of the Week contest. This makes the contest more visible in the community bulletin on the right. Please also look at the Question of the Week Evaluation where we discuss whether this contest should be continued, and what could be improved.


3 Answers 3


Writing tests for code whose purpose I don't understand

IMHO the best questions here are ones which arise from real world software development situations, and this one fits perfectly into this category. Testing and refactoring is clearly and unambiguously within the scope of the site. And the number of votes shows many people here like questions like this.


How to convert the last rc (or other pre-release) into the production version using semver?

A process-level question: Now that I've built and tested v1.2.3-rc.2 of my software, how do I turn that into my v1.2.3 release?


Requirement Specification - How to write an “as much as possible” requisite

Not everything is a clear functional requirement. So how can I express and track soft design constraints?

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .