Picture a row of labelled boxes. The line x = 5 means: find the box labelled x and put 5 inside. If the box already held 3, the 3 is thrown out, because a box holds one value at a time. The line y = x does not tie y to x forever; it looks in x right now, copies the 5 and puts the copy in y. Change x later and y still holds 5.
The order of work is always right side first, then store. Take score = 40 followed by score = score + 10. The computer reads the right side with the old value, 40 + 10 = 50, and only then writes 50 into score. A line that is nonsense in algebra, where no number equals itself plus 10, makes perfect sense in code: the two mentions of score belong to different moments, before and after the update.
Two things look like assignment and are not. In a math equation, x = 5 and 5 = x say the same thing; in code, 5 = x is an error, because you cannot store anything in the number 5. And the test x == 5 stores nothing at all: it asks whether x currently holds 5 and answers true or false.
Think of it like this. Each variable is a small whiteboard with its name written at the top. Assigning means erasing the board and writing the new value, so it only ever shows the latest one, and copying from one board to another copies what is written right now. The picture holds for numbers and text; for lists, many languages copy a link to the same list instead.
Core idea. Assignment is not equality — it's an action. x = x + 1 makes no sense in math, but in programming it means 'update x.'