> you shouldn't have to list every constraint and design descision that led you to that point True, but that logic goes both ways: Unless told otherwise, whoev

> you shouldn't have to list every constraint and design descision that led you to that point True, but that logic goes both ways: Unless told otherwise, whoever reads the question, isn't required to assume that there is a constraint. If I get asked how to water plants with a sieve, without getting told why getting a watering can is impossible, "You don't, use a watering can", is a perfectly acceptable answer. Especially when the question is aked in a question archive, rather than a help-forum. If specific constraints apply to a question, then they should be a part of the question.