when people ask you how you solve the rubik's cube so fast you say. . .

First I tell them to think of a three layer cake, you got to start with a base and work your way up, and I say the facelets are the "icing". I draw a crude "quick sheet". I got the idea online I don't know who first did it, but it loks like it was done with sharpies. I just draw a simple sheet, work through a basic LBL and let them keep the sheet.
 
I say practice, and I am always surprised as to what people's responses are.
Like, Ican't believe that some people think that there is just some pattern that you have to memorize and you just to the same thing over and over again to solve it. [/B]It doesn't take a mathematician to figure that one out!!!!! [/B]
 
First I explain the properties of the cube, then if they are still interested, I tell them to go watch badmephisto or something. Also, if I had trouble teaching them the cross, then I tell them to learn it last, since it is an intuitive step and is hard for people to understand if their mind sees the cube in a certain way. After being forced to see certain cases for algorithms, they might have their vision of the cube changed, and thus have an easier time looking at cross pieces, rather than a giant mess of stickers.
 
person:*brings cube stiff rubiks brand up to me while im using a type a* and he says: Damn son, how do you solve rubiks?
i say: you have to throw it at a wall and i beomes solved.
Person: i dont beileve you.
me : ok, i guess you will never solve it. *i walk away*
10 minutes later: he comes up to me with the cubes in peices and the core broken and says * it didnt work*
:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp
 
person:*brings cube stiff rubiks brand up to me while im using a type a* and he says: Damn son, how do you solve rubiks?
i say: you have to throw it at a wall and i beomes solved.
Person: i dont beileve you.
me : ok, i guess you will never solve it. *i walk away*
10 minutes later: he comes up to me with the cubes in peices and the core broken and says * it didnt work*
:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp

Oh come on dude. You could have just told him how you would do it. Gotta admit, throwing the cube at the wall was stupid.
 
person:*brings cube stiff rubiks brand up to me while im using a type a* and he says: Damn son, how do you solve rubiks?
i say: you have to throw it at a wall and i beomes solved.
Person: i dont beileve you.
me : ok, i guess you will never solve it. *i walk away*
10 minutes later: he comes up to me with the cubes in peices and the core broken and says * it didnt work*
:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp:fp

Oh come on dude. You could have just told him how you would do it. Gotta admit, throwing the cube at the wall was stupid.

I use Rowe's method of breaking in a 2x2, which is throwing it against a wall. It works. Just don't overdo it.
 
I generally tell them that I just looked it up on the internet. If they ask me to teach them (and they seem interested), I say it'd take too long, and they should look it up too, but I'm willing to explain the basic concept. When I'm asked "what the trick is", I say "there are a few sequences of moves you need to learn, and then you just need to know when to use them."
 
Well, now that I can explain certain things... :3

I just run through the steps of CFOP. Sort of one step stop style. It lets them know that there's at least some kind of method to solving, and that it's not all just intuition and brainpower, even if they don't understand the steps ;).
 
In Rubik's cubists' parlance, a memorised sequence of moves that has a desired effect on the cube is called an algorithm. This terminology is derived from the mathematical use of algorithm, meaning a list of well-defined instructions for performing a task from a given initial state, through well-defined successive states, to a desired end-state. Each method of solving the Rubik's Cube employs its own set of algorithms, together with descriptions of what the effect of the algorithm is, and when it can be used to bring the cube closer to being solved.
Most algorithms are designed to transform only a small part of the cube without scrambling other parts that have already been solved, so that they can be applied repeatedly to different parts of the cube until the whole is solved. For example, there are well-known algorithms for cycling three corners without changing the rest of the puzzle, or flipping the orientation of a pair of edges while leaving the others intact.
Some algorithms have a certain desired effect on the cube (for example, swapping two corners) but may also have the side-effect of changing other parts of the cube (such as permuting some edges). Such algorithms are often simpler than the ones without side-effects, and are employed early on in the solution when most of the puzzle has not yet been solved and the side-effects are not important. Towards the end of the solution, the more specific (and usually more complicated) algorithms are used instead, to prevent scrambling parts of the puzzle that have already been solved.
That's exactly what I tell them. I memorized it all from Wikipedia.
 
Back
Top