This question came up recently and was quickly closed as a duplicate of our reference question referenced in the title of this post. I'm not complaining about the reference question: it does a fine job of describing a lot of the problems and solutions one might have in this area.
My (ongoing) problem is that it seems to me that we're often too quick to pull the "duplicate of 'Is there a system...' " trigger. For example, in the question I referenced, the OP's intent was abundantly clear: "How do I analyze a loop that (1) iterates over every other index and (2) the upper limit decreases on every instance of the loop?"
That's not (IMO) answered by the reference question. Rather it was a very specific elementary problem that could be quickly answered with no mention of the reference question. While some people might disagree, I'd also argue that this falls squarely into the cs.SE ballpark of on-topic questions.
I've made this rant before; it's as if a student in my algos class came to my office with that question and I said "Here's a text on algorithm analysis; read the first two chapters and don't let the door hit you on your butt on the way out."
My point here is to again request that we stop and think a bit before hitting the close button. Before I enter duck-and-cover mode I suggest that we say to ourselves, "Does this reference question really address the poster's question, or would a hint or two be more appropriate?"