Here’s a thought: start the lesson with "Ten is not equal to zero, ergo this equation has no solutions. However some people who don't understand math might insist that they can get an answer one way or another. I will now show six possible methods for arriving at an answer, and that none of them work."
In programming, due to the Von Neumann architecture, that equation has always a solution, either a primitive value or a symbol representing the absence of a value. It happens that in programming that statement isn't a equation nor an equality, but an attribution statement where time plays its role. For an initial value of x, lets say x1=20, the resulting value will be x2=30. The programming language reads the existing memory's value of x, 20, sums 10 to it and stores the resulting value, 30, under the same variable name x. I use this example to show my students that mentally processing a program or algorithm it's not the same as reading the math solution of a math problem.