Hacker News new | ask | show | jobs
by alexfromapex 1987 days ago
I had a quiz in middle school where the end of the directions said to ignore everything and put down your pencil. Really wish all schools taught this.
2 comments

It’s good training for test taking in general. Read every question before starting. Then solve the ones you find easy first.

Many people are “bad at tests” because they get stuck on something, panic, waste all their time and then blow the test.

I used to do the opposite, start from the back where the bigger/harder questions where when I was still fresh, and work backwards(?) to the easier questions with fewer points. Agree that leaving a question half finished with enough space to come back to it and finish it is also a good idea, instead of getting stuck and demoralised.

In any case, I think it's fair to say that reading all of the test, thinking about how you want to approach it, and not just blindly following the ordering provided is going to be better than a naive approach - no matter what ordering is chosen.

Indeed - just make sure you read it all first and then solve whatever you find most comfortable solving.

For me I found that doing the ones I knew immediately how to solve first and then going back to the ones I didn’t quite get at first made those easier when revisiting. I think maybe getting my brain into context made referencing that information possible and possibly by reading them and moving on, it gave my brain some time to begin processing them. No idea though.

Same idea applies to IKEA assembly. Read all the directions first.

I had a similar quiz. I never really liked them because it always bothered me why I was expected to follow the last instruction first, regardless of what it said. Even if it said to ignore the previous instructions, I would only be following it once I reached it, which would mean all other instructions had been followed. Nothing in the initial rules that said to read all instructions gave any indication that one should pick and choose which instructions to follow or that you should do them in reverse order.

Perhaps this was the moment when I first started the path to being a programmer.

> I never really liked them because it always bothered me why I was expected to follow the last instruction first, regardless of what it said.

Well then you should be bothered by lots of legal documents/terms of service, many of which say...

"blah blah blah. if you live in california you have specific rights"

A friend told me of a lawyer he knew that would cross out the binding arbitration clause in all legal documents he signed. In california you have the right to opt-out of binding arbitration.

So the last bit of many documents frequently nullifies other things above.

> I never really liked them because it always bothered me why I was expected to follow the last instruction first, regardless of what it said.

I had a similar one, in fairness it started with something along the lines of: "read these instructions completely before you start".

Yes, but you still start with the first instruction.

It is like a function that changes behavior after the first time in executes. The first execution will still do what it says. You have to explicitly call out that you want the last step that modifies the previous steps to be ran first.

It is like when I help someone learning to code and they question why their statement on line 30 doesn't change what is happening on line 15.