Comment by supernova87a

The article doesn't say who should be asking these questions. I hate to say it, but sometimes "ordinary" software programmers (the most dangerous are the kind with just a little experience but not enough to know that they don't know) will start to feel that they should be asking these questions of the people asking them to build something. It's a good sentiment, but often (especially when there are sales/competitive/pre-emptive/other factors) at play, they're straying a little into "too big for your britches" territory and should just build what they're asked to. Leave the questioning to the engineers who both know how to build it in their sleep, and understand why it's needed...