6

You are asking the SE community why a specific vendor (in this case Google) made a decision to favor tool X over tool Y. Honestly, the community here is the wrong audience for such a question. If the Android NDK team at Goole wrote something like GCC in the NDK is now deprecated in favor of Clang. and you want to know their reasoning behind that, you ...


5

We don't provide Google help on Programmers. Sorry. Instead of asking for word definitions so that he can go find his answer someone else, the OP should be doing us the courtesy of asking about the actual problem he's trying to solve. We're here to help people with their conceptual programming problems, not their Google searches. If you're still keen ...


3

I can think of at least 3 variations on how to process these types of images (i.e., image stacking, image replacement, on the fly image masking, etc.). We can only guess at how this was implemented. The question is well worded, with a great example site. That doesn't stop it from being too broad. Just explaining the method you did (image stacking, ...


3

I'm reopening this question unless someone has a good reason why it shouldn't be. We have guidance about history type questions, which (as far as I can remember or find) hasn't been superseded by newer guidance and we have a number of other open and unlocked history questions.


3

Leave Closed I don't think the question should be reopened even after its edit. The answers along the line “get more requirements” might be correct, but they are in no way specific to app health monitoring systems. Maybe we should create a canonical dupe target for “I have to design a program with unclear requirements, what should I do?” where we can ...


2

I don't see a compelling reason for reopening, as long as the question does not get deleted. The topic of the question is IMHO fine in general, though very broad, and it could be seen as a list-of-things question, since there are several reasons for splitting up a larger program into multiple files (performance, however, is none of them). I think it ...


1

Based on the feedback here that the question was too broad, I narrowed the scope to the OP's original case only, and voted to reopen. So definition of question changed from "How should one determine what a health check should actually do when writing one?" with a single specific example to "What should be the scope of a health check for a system ...


1

I still don't think the question should be reopened. I think the edit changes the close reason from "primarily opinion based" to "too broad". The question, in it's new form, can be answered. The answer is "go get better requirements". However, there are entire books on software requirements engineering. Just telling someone that they need to go get better ...


Only top voted, non community-wiki answers of a minimum length are eligible