The ultimate Desmos guide

The slow way

Set the two right-hand sides equal, solve for x, then substitute back to get y. It works, but under time pressure the substitution step is where sign errors sneak in, especially when the answer is not a clean whole number.

Where it goes wrong

• Sign slips when you subtract a negative term.
• Solving for x and forgetting to find y.
• Rearranging into slope-intercept form you never actually needed.
• Missing a second intersection when one of the curves is not a line.

The Desmos move

1. 1Type each equation on its own line. You do not need slope-intercept form. Desmos accepts standard form, point-slope, anything.
2. 2Both graphs appear. A grey dot marks where they cross.
3. 3Click that grey dot. Desmos prints the exact coordinates of the solution.

The slow way

There is no clean algebra for an equation that mixes an exponential and a line. Students either guess and check or build a long table of values, and they still often miscount.

Where it goes wrong

• Assuming one solution when there are really two, or none.
• Spending two minutes on algebra that leads nowhere.
• Arithmetic slips while building a value table by hand.
• Missing a solution hiding at a negative x.

The Desmos move

1. 1Type the equation exactly as written. Desmos marks every x that satisfies it.
2. 2Or graph each side on its own line and count where the two curves cross.
3. 3The number of intersections is your answer. No algebra required.

The slow way

Find the vertex with x = -b/(2a), substitute back for the y-value, then factor or use the quadratic formula for the zeros. Three separate steps, three chances for an arithmetic error.

Where it goes wrong

• A sign mistake in -b/(2a).
• Plugging the x-value back in wrong to get the y-coordinate.
• Reading a minimum as a maximum.
• Factoring trouble when the factor pair is not obvious.

The Desmos move

1. 1Type the quadratic. Desmos graphs it and auto-marks the key points as grey dots.
2. 2Click the dots on the x-axis for the zeros.
3. 3Click the bottom dot for the vertex. Three answers, no algebra.

The slow way

Graph each boundary line, decide which side to shade for each, then find the overlap by hand. Choosing the wrong side to shade is the classic mistake.

Where it goes wrong

• Flipping the inequality when you divide by a negative.
• Shading the wrong side of the line.
• Losing track of whether the boundary is included.
• Checking only one of the two conditions.

The Desmos move

1. 1Type each inequality on its own line. Desmos shades each region for you.
2. 2Strict inequalities get a dashed boundary, inclusive ones a solid boundary.
3. 3The darker, overlapping area is the solution set for the whole system.

The slow way

Split into two equations, 2x - 5 = 7 and 2x - 5 = -7, solve each, and check both. The negative case is the one that quietly gets dropped.

Where it goes wrong

• Forgetting the negative case entirely.
• A sign error inside the negative case.
• Mixing up the two solutions when a trap answer looks similar.
• Using the wrong branch of a piecewise function at the boundary.

The Desmos move

1. 1Type the absolute-value equation directly. Desmos draws a vertical line at each solution.
2. 2For a piecewise function, use the brace syntax with each branch and its condition.
3. 3Read both branches and the transition point right off the graph.

The slow way

Set the expressions equal, rearrange to a quadratic, set its discriminant to zero, and solve for k. The discriminant setup is fragile and slow.

Where it goes wrong

• Building the discriminant equation with the wrong coefficient.
• Arithmetic slips under the square root.
• Reading exactly one solution as a specific intersection point.
• Forgetting that tangent means touching once, not just crossing once.

The Desmos move

1. 1Type the line with the unknown as a letter. Desmos offers to add a slider for k. Accept it.
2. 2Type the curve on the next line.
3. 3Drag the k slider until the line just kisses the curve at one point. Read k off the slider.

The slow way

Add everything up and divide for the mean, then sort the list and pick the middle for the median. Doable, but sums and sorts are easy to fumble when the numbers are messy.

Where it goes wrong

• Addition errors in the sum.
• Mis-sorting the list for the median.
• Averaging the wrong two middle values on an even-length list.
• Confusing sample versus population standard deviation.

The Desmos move

1. 1Define your data as a list with square brackets.
2. 2On new lines, call mean(L), median(L), stdev(L), and so on. Desmos sorts internally, so order does not matter.
3. 3Each line returns its value immediately.

The slow way

Complete the square in x, complete the square in y, and rewrite in center-radius form. The constant you add to balance each square is the part everyone forgets.

Where it goes wrong

• Not adding the completing-the-square constants to the other side.
• A sign error on the center coordinates.
• Square-rooting the wrong number for the radius.
• Misreading the center when h or k is negative.

The Desmos move

1. 1Type the equation in its expanded form, exactly as given. No rearranging.
2. 2Desmos draws the circle immediately.
3. 3The center is the middle of the circle, and you can read the radius off the gridlines from edge to center.

The slow way

Check first differences, then second differences, decide the model type, then set up and solve a system of three equations for the coefficients. Four minutes with lots of room to slip.

Where it goes wrong

• Using an equals sign instead of the tilde, so the regression never runs.
• Writing x and y instead of x_1 and y_1.
• Ignoring r-squared and never checking the fit.
• Choosing the wrong model family.

The Desmos move

1. 1Press Ctrl/Cmd + Alt + T to open a table. Put the x values in the x_1 column and the y values in y_1.
2. 2On a new line, type the model with a tilde, not an equals sign: y_1 ~ mx_1 + b for a line.
3. 3Desmos fits it and reports the coefficients plus r-squared. If the fit is poor, swap to a quadratic or exponential model.

The slow way

Set the two equal, rearrange to a quadratic, set the discriminant to zero, and solve. About three minutes, and the discriminant is where most of the errors live.

Where it goes wrong

• Setting up the discriminant with the wrong coefficient.
• Reporting only the positive k and missing the negative one.
• Confusing one solution with a specific point.
• Dropping a factor of 2 in the quadratic term.

The Desmos move

1. 1Graph the line with the parameter as a letter and add the slider Desmos offers.
2. 2Graph the curve on the next line.
3. 3Drag the slider. When the two intersections merge into one grey dot, that is your value. Watch for a matching value on the other side.

The slow way

Plug each choice into the expression one at a time and check whether it gives zero. Four substitutions, each its own little arithmetic risk.

Where it goes wrong

• An arithmetic error when a choice is a fraction.
• Testing in an unlucky order and running out of time.
• Misreading -1 as 1 under pressure.
• Checking only part of the expression.

The Desmos move

1. 1Press Ctrl/Cmd + Alt + T for a table. Put all four answer choices in the x_1 column.
2. 2Click the y_1 header and type the expression in terms of x_1.
3. 3Desmos evaluates every row at once. Scan for the row that returns the target value.

The slow way

FOIL it out and match against the choices. Quick, but the middle-term sign is the spot where a careless slip flips the answer.

Where it goes wrong

• Combining like terms wrong and getting +x instead of -x.
• Dropping the constant under time pressure.
• Checking a second choice after you already found the match.
• Talking yourself out of the correct sign.

The Desmos move

1. 1Graph the original expression on line one.
2. 2Graph each answer choice on its own line.
3. 3The equivalent one draws exactly on top of the original, so the two curves look like one. The others sit visibly apart.