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


How do I handle disagreement in a code review regarding an unlikely edge case?

Code reviews and decisions which edge cases to handle in unit tests are clearly within the scope, the question is well written, and it is not a hypothetical case but a problem from a real-world situation. Moreover, the number of votes for the question as well as for the answers show our community likes to see more questions of this kind.


Anemic REST and DDD

A design-level question. How fine-grained should our URL structure be when designing a REST API?


WHEN is it most appropriate for a Development Team to create/update their definition of “Done”?

A process-level question. Very simple but also very important. I think this kind of question is a perfect example of the “Wiki” aspect in the original Stack Exchange concept.

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