ghong14 Wrote:Any suggestions?
Just one: Quit putting obstacles in your own path. Seriously, just pick up the proverbial shovel and start digging.
You're looking for 18 point blah blah blah ugly decimal thing. Or, alternatively, 200/11 (there's not really any good solid reason to decimal-ize this in the first place).
So...
(A) This will be an integer, so it's wrong.
(B) This will be an integer, so it's wrong.
(C) This will be an integer, so it's wrong.
(D) is 100 x 20/110 = 2000/110. No need to divide anything, that's definitely the same as 200/11.
(E) is 100 x 101/110, which is going to be awfully close to 100, and therefore nowhere close to the goal number.
There, you're done. That took... what, ten seconds to plug those numbers? Maybe fifteen seconds, if you're really sleepy, tired, and distracted.
Seriously, the test already puts enough obstacles in your way; the last thing you need is
more obstacles.
DO NOT EVER forgo a problem-solving method because you're thinking, "oh, that's not pretty" or "oh, that might take too long".
Just DO IT.That's it. Really, I promise you. Don't make this any more complicated than it needs to be.
In the
extremely unlikely event that your method
does turn out to take a really long time, then you can always quit; no one is holding a gun to your head.
But, in most cases -- like this one -- you'll find that the "un-pretty" things that you were so afraid of won't take more than a small fraction of a minute.
In fact, in most cases, sitting there and worrying about how long something will take will actually take longer than just doing the thing in the first place!
Yeah.