Common Mistakes in Algebra Fundamentals

392 common pitfalls across 98 concepts, including 98 recurring stuck points

These are the pitfalls students hit across all 98 algebra fundamentals concepts, from Variables, Expressions and Equations onward. Each entry names the concept it comes from, so you can tell a slip from a genuine gap and go straight to the explanation.

1
Variables
Stuck Point

The procedure for variables is the easy part; the trap is treating x as always meaning the same number across different problems. Asking "Is a letter being used to hold a number we don't know yet or one that can vary?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

2
Variables
Mistake

Treating x as always meaning the same number across different problems - a variable's value is set by its own equation, not fixed forever.

3
Variables
Mistake

Reading the letter as the answer instead of a placeholder - the variable names the unknown; solving reveals the number.

4
Variables
Mistake

Thinking different letters must mean different numbers - x and y can happen to equal the same value.

5
Expressions
Stuck Point

The procedure for expressions is the easy part; the trap is trying to solve an expression. Asking "Is there a combination of terms with NO equals sign, so the only moves are simplify or evaluate?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

6
Expressions
Mistake

Trying to solve an expression - with no equals sign there is nothing to make true, so you can only simplify or evaluate.

7
Expressions
Mistake

Combining terms that are not alike, like adding 2x and 3 - only like terms (same variable part) can be combined.

8
Expressions
Mistake

Dropping a sign when simplifying, e.g. 5−2x becoming 3x - the subtraction and the term stay attached.

9
Equations
Stuck Point

The procedure for equations is the easy part; the trap is operating on one side only. Asking "Are two expressions joined by = with an unknown I'm asked to make the statement true?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

10
Equations
Mistake

Operating on one side only - whatever you add, subtract, multiply, or divide must hit both sides to keep balance.

11
Equations
Mistake

Forgetting to check the answer - substitute it back; a true statement confirms the solution.

12
Equations
Mistake

Treating = as 'compute the answer next' (calculator habit) - in algebra = means the two sides are the same quantity.

13

The procedure for solving linear equations is the easy part; the trap is doing an operation to only one side. Asking "Is there an equals sign and a variable value to find?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

14

Doing an operation to only one side — preserve equality by doing the same operation to both sides.

15

Combining unlike terms — only combine terms with the same variable part.

16

Stopping before checking — substitute the solution back into the original equation.

17
Inequalities
Stuck Point

The procedure for inequalities is the easy part; the trap is forgetting to flip the symbol when multiplying or dividing by a negative. Asking "Is the relation 'less/greater than (or equal)' so the answer is a range, not a single value?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

18
Inequalities
Mistake

Forgetting to flip the symbol when multiplying or dividing by a negative - reverse < to > (and vice versa) in that step.

19
Inequalities
Mistake

Writing one number as the answer - an inequality's solution is a range, shown on a number line or in interval form.

20
Inequalities
Mistake

Confusing open and closed dots - <,> use an open circle (not included); ≤,≥ use a filled circle (included).

21
Coordinate Plane
Stuck Point

The procedure for coordinate plane is the easy part; the trap is reversing the coordinates. Asking "Am I locating or drawing a position using a horizontal value paired with a vertical value?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

22

Reversing the coordinates - (x,y) is always (horizontal, vertical); (3,2)≠(2,3).

23

Mixing up quadrant signs - quadrant II is (−,+), quadrant III is (−,−); check both signs.

24

Starting from a point other than the origin - every address is measured from (0,0).

25
Slope
Stuck Point

The procedure for slope is the easy part; the trap is computing ΔxΔy instead of ΔyΔx. Asking "Does the output change by the same amount for each equal step in the input?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

26
Slope
Mistake

Computing ΔxΔy instead of ΔyΔx — rise goes over run, output over input.

27
Slope
Mistake

Subtracting the coordinates in a different order top and bottom — keep (y2−y1) over (x2−x1) with the same first point.

28
Slope
Mistake

Calling a curved or unequal-step relationship a slope — slope only describes a straight line.

29
Linear Functions
Stuck Point

The procedure for linear functions is the easy part; the trap is calling every equation with x linear. Asking "Does the output change by the same amount each time the input step is the same?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

30

Calling every equation with x linear — check for constant rate and no powers like x2.

31

Confusing slope with y-intercept — slope is the repeated change, while the y-intercept is the starting value when the input is 0.

32

Using two points without checking the whole pattern — a line through two points is linear, but a table or story still needs every equal input step to fit the same rate.

33

The procedure for systems of equations is the easy part; the trap is solving only one equation and ignoring the other. Asking "Does the answer need to make every equation true?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

34

Solving only one equation and ignoring the other — a system solution must satisfy all equations.

35

Treating the intersection as just an x value — for two-variable systems, the solution is an ordered pair.

36

Using substitution or elimination without aligning variables — keep equations equivalent at each step.

37

The procedure for quadratic functions is the easy part; the trap is forgetting a may be negative. Asking "Is the highest power of the variable exactly 2, so the graph curves into a parabola?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

38

Forgetting a may be negative - then the parabola opens downward and has a maximum, not a minimum.

39

Reading the vertex from the standard form directly - use x=−b2a or convert to a(x−h)2+k.

40

Expecting one x-value per y - a horizontal line can cross a parabola twice, so two inputs can share an output.

41
Quadratic Formula
Stuck Point

The procedure for quadratic formula is the easy part; the trap is using the formula before setting the equation to zero. Asking "Do I have a quadratic equation set to zero whose exact solutions I need?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

42

Using the formula before setting the equation to zero - rearrange to ax2+bx+c=0 first.

43

Mishandling signs of b in −b - if b=−4, then −b=+4.

44

Dropping the ± and reporting one root - the ± produces two solutions.

45
Polynomials
Stuck Point

The procedure for polynomials is the easy part; the trap is counting an expression with a negative or fractional exponent as a polynomial. Asking "Is every exponent on the variable a whole number ≥0 with no variable in a denominator?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

46
Polynomials
Mistake

Counting an expression with a negative or fractional exponent as a polynomial - powers must be whole numbers ≥0.

47
Polynomials
Mistake

Misreading the degree - it's the highest power present, not the number of terms.

48
Polynomials
Mistake

Forgetting to combine like terms before naming degree or leading coefficient - simplify to standard form first.

49
Factoring
Stuck Point

The procedure for factoring is the easy part; the trap is forgetting to pull out the greatest common factor first. Asking "Am I rewriting an expression as a product of simpler factors that multiply back to it?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

50
Factoring
Mistake

Forgetting to pull out the greatest common factor first - factor out the GCF before any other pattern.

51
Factoring
Mistake

Sign errors in the binomials - for x2−5x+6 both factors are negative: (x−2)(x−3).

52
Factoring
Mistake

Assuming every quadratic factors over integers - if no integer pair works, switch to the quadratic formula.

53

The procedure for variable as placeholder is the easy part; the trap is thinking the placeholder can be any number. Asking "Does the condition pin the variable to one specific value I'm meant to find?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

54

Thinking the placeholder can be any number - the equation constrains it to one specific value.

55

Treating the letter as the final answer - it names the unknown; solving reveals the number.

56

Forgetting to verify by substitution - plug the value back to confirm it fits the condition.

57

The procedure for variable as generalization is the easy part; the trap is solving a generalization for a value. Asking "Is the letter meant to stand for ANY value, making the statement true universally?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

58

Solving a generalization for a value - there's no single solution; it holds for all values.

59

Plugging in one number and concluding it's proven - one case doesn't establish a 'for all' claim.

60

Confusing it with a placeholder - a generalization means ANY value, not one specific unknown.

61
Evaluation
Stuck Point

The procedure for evaluation is the easy part; the trap is ignoring order of operations after substituting. Asking "Are the variable's values given so I just substitute and compute one number?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

62
Evaluation
Mistake

Ignoring order of operations after substituting - compute exponents and multiplication before addition.

63
Evaluation
Mistake

Forgetting parentheses around the substituted value - write 2(3)+1, not 23+1.

64
Evaluation
Mistake

Confusing evaluating with solving - evaluation needs given values; solving finds unknown ones.

65
Substitution
Stuck Point

The procedure for substitution is the easy part; the trap is dropping parentheses around the substituted expression. Asking "Am I replacing a variable with an EQUAL expression everywhere it appears?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

66
Substitution
Mistake

Dropping parentheses around the substituted expression - wrap it so grouping survives.

67
Substitution
Mistake

Replacing only some occurrences of the variable - substitute every occurrence consistently.

68
Substitution
Mistake

Substituting a value when the variable is still unknown - solve for it first, then substitute.

69

The procedure for identity vs equation is the easy part; the trap is calling every equation an identity. Asking "Does the equality hold for EVERY value of the variable, or only for special ones?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

70

Calling every equation an identity - test more than one value; an identity must hold for all.

71

Interpreting 0=0 as no solution - it means every value works (an identity).

72

Trying to find a single answer to an identity - there isn't one; it's universally true.

73
Solution Concept
Stuck Point

The procedure for solution concept is the easy part; the trap is skipping the check. Asking "Does plugging this value back into the original statement make it true?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

74

Skipping the check - substitute the candidate back to confirm it makes the statement true.

75

Accepting an extraneous solution - values introduced by squaring or clearing denominators must be verified.

76

Confusing a solution with the expression's value - a solution makes a statement TRUE, not just produces a number.

77
Solution Set
Stuck Point

The procedure for solution set is the easy part; the trap is giving one value when there are many. Asking "Am I describing EVERY value that satisfies the statement, not just one?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

78
Solution Set
Mistake

Giving one value when there are many - inequalities and quadratics often have whole ranges or multiple answers.

79
Solution Set
Mistake

Forgetting the empty set is a valid answer - if nothing satisfies it, write ∅.

80
Solution Set
Mistake

Mixing up open and closed brackets in interval notation - ( excludes the endpoint, [ includes it.

81
Constraint System
Stuck Point

The procedure for constraint system is the easy part; the trap is satisfying some constraints but not all. Asking "Must the same values satisfy multiple conditions at the same time?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

82

Satisfying some constraints but not all - the answer must meet every condition simultaneously.

83

Ignoring inequality constraints once an equation is solved - check the solution against the inequalities too.

84

Treating the conditions as alternatives - they're joined by AND, so all must hold, not just one.

85
Proportional Line
Stuck Point

The procedure for proportional line is the easy part; the trap is calling a line with a nonzero y-intercept proportional. Asking "Does the line pass through (0,0) with y/x the same for every point?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

86

Calling a line with a nonzero y-intercept proportional - proportional lines must pass through the origin.

87

Confusing the constant ratio k with the intercept - k is the slope here, and the intercept is 0.

88

Checking only one point for a constant ratio - y/x=k must hold for every point on the line.

89

The procedure for rate of change (algebraic) is the easy part; the trap is subtracting the points in inconsistent order. Asking "Am I dividing a change in output by a change in input over an interval?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

90

Subtracting the points in inconsistent order - keep f(x2)−f(x1)x2−x1 with the same first point on top and bottom.

91

Treating the average over a curve as a single constant rate - it's only the average between the two chosen points.

92

Dividing inputs by outputs - it's change in output over change in input, not the reverse.

93

The procedure for algebraic representation is the easy part; the trap is using the same letter for two different quantities. Asking "Can I name the varying quantity with a letter and write the relationship as an equation?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

94

Using the same letter for two different quantities - give each varying quantity its own letter and write what it stands for.

95

Putting the fixed number where the rate belongs - the 'per each' amount multiplies the variable; the one-time amount stands alone.

96

Representing a constant as a variable - only the quantity that actually changes gets a letter.

97

The procedure for symbolic abstraction is the easy part; the trap is trying to solve a universal identity for a value. Asking "Am I making a claim meant to hold for every value, not just the numbers in front of me?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

98

Trying to solve a universal identity for a value - an identity like a+b=b+a is true for all values, so there is nothing to solve.

99

Generalizing from one example - a single case does not prove a 'for all' claim; the letters must cover every case.

100

Reusing one letter to mean two different things - each abstracted symbol must stand for the same quantity throughout.

101

The procedure for rewriting expressions is the easy part; the trap is distributing to only the first term. Asking "Are these two expressions equal at every value of the variable, just written differently?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

102

Distributing to only the first term - 2(x+3)=2x+6, not 2x+3; the factor hits every term inside.

103

Combining unlike terms - 3x+2 does not simplify to 5x; only matching terms combine.

104

Changing the value instead of just the form - check by plugging in one number; both forms must agree.

105

The procedure for factoring intuition is the easy part; the trap is finding numbers that add to b but ignore the product. Asking "Am I turning a sum of terms into a product of simpler factors?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

106

Finding numbers that add to b but ignore the product - the pair must satisfy both p+q=b and pq=c.

107

Mixing up signs - for x2−5x+6 both numbers are negative (−2,−3); check the sign of c and b.

108

Forgetting a common factor first - pull out shared factors before hunting for the pair, e.g. 2x2+10x+12=2(x2+5x+6).

109

The procedure for expansion intuition is the easy part; the trap is dropping the cross term when squaring. Asking "Am I turning a product of factors into a sum of terms by distributing?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

110

Dropping the cross term when squaring - (a+b)2=a2+2ab+b2 has a middle 2ab, not just a2+b2.

111

Distributing to only one term - every term in the first factor multiplies every term in the second.

112

Forgetting to combine like terms - after FOIL, add the inner and outer terms (3x+2x=5x).

113

The procedure for equivalence transformation is the easy part; the trap is changing only one side. Asking "Does this step act on both sides equally so the solution set is unchanged?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

114

Changing only one side - whatever you add, subtract, multiply, or divide must hit both sides.

115

Multiplying or dividing by zero - the multiplier must be nonzero or solutions are lost.

116

Doing different operations to each side - the SAME operation with the SAME number must apply to both.

117
Isolating Variable
Stuck Point

The procedure for isolating variable is the easy part; the trap is undoing multiplication before addition. Asking "Am I peeling operations off the variable until it stands alone on one side?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

118

Undoing multiplication before addition - reverse the evaluation order: strip the added constant first, then the coefficient.

119

Dividing only part of a side - when you divide by the coefficient, divide every term on both sides.

120

Applying the inverse to one side only - each peel is a both-sides operation.

121

The procedure for dependent vs independent variables is the easy part; the trap is swapping the axes. Asking "Which quantity do I choose freely, and which one is then determined by it?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

122

Swapping the axes - independent goes on the horizontal x-axis, dependent on the vertical y-axis.

123

Assuming the dependent variable can be chosen - only the independent input is free; the output follows the rule.

124

Confusing correlation direction - the dependent quantity responds to the independent one, not the reverse.

125

The procedure for modeling with equations is the easy part; the trap is flipping subtraction order. Asking "Am I turning a described situation into an equation I can then solve for the unknown?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

126

Flipping subtraction order - '7 less than x' is x−7, not 7−x; translate meaning, not word order.

127

Skipping the 'let x =' definition - state exactly what the variable represents before writing the equation.

128

Ignoring a stated constraint - every condition in the story must appear in the model.

129
Parameter
Stuck Point

The procedure for parameter is the easy part; the trap is treating the parameter as the input variable. Asking "Is this quantity held constant within one case but changed to produce a different member of a family?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

130
Parameter
Mistake

Treating the parameter as the input variable - within one line, m and b are fixed while x varies.

131
Parameter
Mistake

Treating a parameter as a universal constant - parameters change between cases; constants like π never do.

132
Parameter
Mistake

Solving for the parameter as if it were the unknown - to find m,b you typically use given points, not isolate them from one equation.

133

The procedure for constant vs variable is the easy part; the trap is trying to solve for a named constant. Asking "Could this symbol's value be different in another situation, or is it locked forever?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

134

Trying to solve for a named constant - π and e have fixed values; you never isolate them.

135

Assuming every letter is a variable - letters like c or k often stand for fixed unknown constants.

136

Forgetting context - the same letter can be a constant in one problem and a variable in another.

137
Degrees of Freedom
Stuck Point

The procedure for degrees of freedom is the easy part; the trap is counting dependent equations as constraints. Asking "After applying all independent constraints, how many values can I still choose freely?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

138

Counting dependent equations as constraints - only independent equations reduce r; redundant ones don't.

139

Forgetting that more variables than equations means free choices - n−r>0 gives infinitely many solutions, provided the equations do not contradict each other.

140

Confusing zero degrees with a guaranteed unique solution - n−r=0 only allows uniqueness; a contradiction can still make S=∅.

141

The procedure for linear system behavior is the easy part; the trap is equating 'two equations' with 'one solution'. Asking "Am I classifying how many solutions a linear system has by how its lines relate?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

142

Equating 'two equations' with 'one solution' - parallel or coincident lines break that assumption.

143

Confusing parallel with coincident - equal slope and different intercept is parallel (none); equal everything is the same line (infinite).

144

Solving before checking - compare coefficient ratios first to spot no-solution or infinite-solution cases.

145
Consistency
Stuck Point

The procedure for consistency is the easy part; the trap is equating consistency with a unique solution. Asking "Is there at least one set of values that makes every equation true at the same time?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

146
Consistency
Mistake

Equating consistency with a unique solution - infinitely many solutions still counts as consistent.

147
Consistency
Mistake

Calling a system inconsistent because it has free variables - free variables mean many solutions, not zero.

148
Consistency
Mistake

Missing the 0=c signal - a false numeric statement during elimination means inconsistent, stop solving.

149
Redundancy
Stuck Point

The procedure for redundancy is the easy part; the trap is counting a redundant equation as a real constraint. Asking "Is this equation just a combination of the others, telling me nothing new?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

150
Redundancy
Mistake

Counting a redundant equation as a real constraint - it leaves r unchanged; the system is less constrained than it looks.

151
Redundancy
Mistake

Confusing redundant with contradictory - all ratios equal is redundant (0=0); equal slopes but unequal constants is contradictory (0=c).

152
Redundancy
Mistake

Expecting a unique solution from duplicate equations - redundancy typically leaves free variables and infinitely many solutions.

153
Contradiction
Stuck Point

The procedure for contradiction is the easy part; the trap is reading 0=0 as a contradiction. Asking "Have I reached a statement that no values could ever make true?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

154

Reading 0=0 as a contradiction - 0=0 is always true (redundant); only 0=c with c≠0 is a contradiction.

155

Continuing to solve after a contradiction - once you hit 0=5, stop: there is no solution.

156

Forgetting a contradiction can come from a setup error - recheck arithmetic before declaring no solution.

157
Algebraic Symmetry
Stuck Point

The procedure for algebraic symmetry is the easy part; the trap is assuming any expression with both variables is symmetric. Asking "If I swap the two variables, do I get back the exact same expression?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

158

Assuming any expression with both variables is symmetric - actually swap and compare; x2+xy fails.

159

Confusing symmetry with the commutative property - symmetry is about an expression's invariance, not an operation's reordering.

160

Checking only one term - every term must survive the swap for the whole expression to be symmetric.

161

The procedure for dimensional consistency is the easy part; the trap is adding terms with different units. Asking "Does every term being added or equated carry the same units?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

162

Adding terms with different units - only quantities with the same dimensions can be added or equated.

163

Ignoring units because the arithmetic works - matching numbers don't guarantee matching dimensions.

164

Forgetting to check both sides - [LHS] must equal [RHS], not just the terms within one side.

165
Symbolic Overload
Stuck Point

The procedure for symbolic overload is the easy part; the trap is reading '−x' as automatically negative. Asking "Does this symbol have more than one possible meaning that only context resolves?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

166

Reading '−x' as automatically negative - it means 'opposite of x,' which is positive when x is negative.

167

Assuming a symbol's meaning is fixed everywhere - check the surrounding context each time.

168

Confusing the negative sign with subtraction - −3 labels a number; 5−3 is an operation between two.

169

The procedure for structure vs computation is the easy part; the trap is computing first and missing the shortcut. Asking "Can I solve this by recognizing its form instead of grinding through the arithmetic?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

170

Computing first and missing the shortcut - scan for a recognizable form before doing arithmetic.

171

Forcing a pattern that isn't there - confirm the form actually matches before applying it.

172

Treating structural insight as 'not real math' - recognizing form is the higher-leverage skill, not a shortcut to skip.

173

The procedure for expression simplification is the easy part; the trap is combining unlike terms like 3x2+5x into one term. Asking "Am I making one expression cleaner without changing its value (no equation to solve)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

174

Combining unlike terms like 3x2+5x into one term - only terms with the same variable AND same exponent combine.

175

Adding the exponents when combining like terms (3x2+5x2=8x4) - the exponent stays the same; only coefficients add.

176

Forgetting to distribute a leading minus or coefficient before combining - clear parentheses first, then combine.

177
Algebraic Pattern
Stuck Point

The procedure for algebraic pattern is the easy part; the trap is forcing a2+b2 to factor as (a+b)(a−b). Asking "Does this expression match the template of a known identity slot-for-slot?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

178

Forcing a2+b2 to factor as (a+b)(a−b) - only the DIFFERENCE of squares factors; the sum does not over the reals.

179

Mismatching the cube signs (a3−b3 vs a3+b3) - SOAP: the middle term sign is Opposite the binomial sign, the last is Always Positive.

180

Missing that a coefficient is a perfect square (49x2=(7x)2) - check whether each piece is itself a square or cube before deciding the pattern fits.

181

The procedure for functional dependency is the easy part; the trap is allowing one input to give two outputs and still calling it a function. Asking "Does every allowed input produce exactly one output (never two)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

182

Allowing one input to give two outputs and still calling it a function - apply the vertical line / one-output test.

183

Confusing dependency with causation - y=f(x) says x determines y mathematically, not that x physically causes y.

184

Swapping which variable is the input - the dependent (output) variable is the one being computed FROM the independent (input) one.

185
Abstraction Level
Stuck Point

The procedure for abstraction level is the easy part; the trap is proving a universal claim by checking a few examples. Asking "Is this claim about one particular case, or about every object of its kind?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

186

Proving a universal claim by checking a few examples - examples can suggest but never prove a 'for all' statement.

187

Disproving a general rule and thinking you must check more cases - a single counterexample is enough to kill a universal claim.

188

Confusing a concrete instance with the general law it illustrates - 2+3=3+2 is one case of commutativity, not the law a+b=b+a itself.

189

The procedure for algebra as language is the easy part; the trap is reading 5x as a concatenated number or 'five and x'. Asking "Am I treating these symbols as a language with grammar that must be read or written correctly?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

190

Reading 5x as a concatenated number or 'five and x' - adjacency in algebra means multiplication.

191

Translating 'less than' in original word order - '3 less than x' is x−3, not 3−x; the language reverses it.

192

Writing grammatically broken notation like =3x+ - every expression must be a well-formed sentence in the language.

193

The procedure for algebra as structure is the easy part; the trap is assuming every operation is commutative or associative. Asking "Is the question about the properties of an operation, rather than computing a number?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

194

Assuming every operation is commutative or associative - structure means you must CHECK each property, not assume it (matrix multiplication is not commutative).

195

Confusing the identity element with zero specifically - the identity is whatever leaves elements unchanged under THAT operation (1 for multiplication).

196

Treating structure as just harder number-crunching - the object of study is the property/behavior, not a numerical answer.

197

The procedure for algebraic invariance is the easy part; the trap is assuming all features are invariant under a transformation. Asking "Does this quantity stay exactly the same after the allowed transformation is applied?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

198

Assuming all features are invariant under a transformation - state WHICH transformation and check each quantity separately.

199

Confusing 'the expression changed' with 'the invariant changed' - the form can change while the invariant (e.g. degree) stays fixed.

200

Calling a number invariant without naming the transformation - invariance is always relative to a specified allowed operation.

201

The procedure for algebraic constraint is the easy part; the trap is ignoring implicit constraints like denominator ≠0 or radicand ≥0. Asking "Does this condition restrict the set of permissible values rather than ask for a single computation?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

202

Ignoring implicit constraints like denominator ≠0 or radicand ≥0 - always exclude values that break the expression.

203

Treating a constraint as a single answer - a constraint defines a SET of allowed values, often infinitely many.

204

Mixing up ≤ and < at the boundary - a closed inequality includes the boundary value, a strict one excludes it.

205
Binomial Theorem
Stuck Point

The procedure for binomial theorem is the easy part; the trap is distributing the exponent as (a+b)n=an+bn. Asking "Am I raising a two-term expression to a whole-number power and want its expansion or a single term?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

206

Distributing the exponent as (a+b)n=an+bn - every cross term with (nk) is required.

207

Letting the a and b exponents not sum to n - in each term an−kbk the powers must total n.

208

Forgetting the coefficient on a chosen term - the term is (nk)an−kbk, not just an−kbk.

209

The procedure for quadratic standard form is the easy part; the trap is forgetting a≠0. Asking "Is this a single-variable degree-2 equation written as everything-minus-everything =0 with a≠0?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

210

Forgetting a≠0 - if the x2 coefficient is 0 it is linear, not quadratic.

211

Reading off a,b,c before collecting like terms or moving everything to one side - get it to ⋯=0 first.

212

Misreading c when the equation is not set to zero - subtract the right side over so the constant on the left is the true c.

213

The procedure for quadratic vertex form is the easy part; the trap is taking h with the wrong sign. Asking "Is the quadratic written as a squared binomial plus a constant, and do I want its turning point?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

214

Taking h with the wrong sign - (x−h) means h is the value that makes the inside zero, so (x+3)2 has h=−3.

215

Forgetting a also flips/stretches - a negative a opens the parabola downward (vertex is a maximum).

216

Reading (h,k) from standard form - convert to a(x−h)2+k first; the vertex is not the b and c.

217

The procedure for quadratic factored form is the easy part; the trap is reading roots with the wrong sign. Asking "Is the quadratic written as a product of linear factors, and do I want where it equals zero?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

218

Reading roots with the wrong sign - the root of (x−r) is +r, so (x+2) gives root −2.

219

Ignoring the leading factor a - a does not change the roots but is needed to match the full function.

220

Setting the whole product equal to a nonzero number and 'solving' each factor - the zero-product trick only works when the product equals 0.

221

The procedure for completing the square is the easy part; the trap is adding (b2)2 without also subtracting it. Asking "Am I manufacturing a perfect-square trinomial by adding and subtracting the same value to keep it equal?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

222

Adding (b2)2 without also subtracting it - you must keep the expression equal; add and subtract the same amount.

223

Adding (b/2)2 without first factoring out a leading coefficient a≠1 — factor out a, complete the square inside, then distribute.

224

Halving b but not squaring it - the value added is the SQUARE of half the middle coefficient.

225
Discriminant
Stuck Point

The procedure for discriminant is the easy part; the trap is computing b2−4ac with the wrong sign on b. Asking "Do I only need to know how many/what kind of roots a quadratic has, not their values?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

226
Discriminant
Mistake

Computing b2−4ac with the wrong sign on b - b2 is always nonnegative, so square the value of b carefully (e.g. (−5)2=25).

227
Discriminant
Mistake

Dropping the −4ac - the discriminant is the whole b2−4ac, not just b2.

228
Discriminant
Mistake

Saying 'no solutions' when Δ<0 - there are no REAL solutions, but two complex ones.

229
Graphing Parabolas
Stuck Point

The procedure for graphing parabolas is the easy part; the trap is getting the opening direction wrong. Asking "Am I producing or reading a picture of a quadratic, using vertex, axis, and intercepts?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

230

Getting the opening direction wrong - a>0 opens up, a<0 opens down; check the sign first.

231

Using x=b2a for the axis - the axis is x=−b2a (note the minus).

232

Connecting points with straight segments - a parabola is a smooth curve, not a polygon.

233

The procedure for vertex and axis of symmetry is the easy part; the trap is reporting only the x-coordinate as 'the vertex'. Asking "Am I after the turning point or the mirror line of a parabola?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

234

Reporting only the x-coordinate as 'the vertex' - the vertex is the point (h,k); plug h back to get k.

235

Writing the axis of symmetry as a number instead of an equation - it is the line x=h.

236

Using x=b2a - the axis/vertex x-coordinate is −b2a.

237

The procedure for zeros of a quadratic is the easy part; the trap is taking only the + branch of ±. Asking "Am I looking for the x-values that make the quadratic equal zero?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

238

Taking only the + branch of ± - a quadratic generally has two zeros; keep both signs.

239

Reporting the zeros with flipped signs from factors - (x−3) gives zero 3, (x+5) gives zero −5.

240

Calling 'no real zeros' an error - when Δ<0 the parabola simply does not cross the x-axis.

241

The procedure for polynomial addition and subtraction is the easy part; the trap is adding exponents instead of coefficients. Asking "Am I joining two polynomials with + or − and merging only same-power terms?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

242

Adding exponents instead of coefficients - 3x2+5x2=8x2; the exponent stays.

243

Not distributing the subtraction sign to every term of the second polynomial - −(2x−5)=−2x+5.

244

Combining unlike terms like x2 and x - only identical variable-and-power terms merge.

245

The procedure for polynomial multiplication is the easy part; the trap is squaring a binomial as a2+b2. Asking "Am I multiplying expressions so that every term in one meets every term in the other?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

246

Squaring a binomial as a2+b2 - (a+b)2=a2+2ab+b2 includes the cross term.

247

Missing a cross-product term (forgetting Outer or Inner in FOIL) - every term must meet every term.

248

Adding exponents wrong when multiplying terms - x2⋅x3=x5 (add exponents only when MULTIPLYING).

249

The procedure for factoring out the gcf is the easy part; the trap is taking the highest variable power instead of the lowest. Asking "Do all terms share a numerical and/or variable factor I can lift to the front?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

250

Taking the highest variable power instead of the lowest - the common variable factor is the SMALLEST exponent present.

251

Forgetting a term's leftover, e.g. factoring 6x2+3x as 3x(2x) drops the +1; it should be 3x(2x+1) - every original term must reappear inside the parentheses.

252

Not pulling the largest numerical factor - 6x+9 has GCF 3, not 1; take the greatest common number too.

253

The procedure for factoring difference of squares is the easy part; the trap is trying to factor a2+b2 the same way. Asking "Are both terms perfect squares with a minus sign between them and nothing in the middle?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

254

Trying to factor a2+b2 the same way — a sum of squares does not factor over the reals; only the difference does.

255

Stopping after one step on x4−16 — refactor the new difference of squares: (x2−4)(x2+4)=(x−2)(x+2)(x2+4).

256

Forgetting a coefficient is a square too — 4x2−9 has a=2x, b=3, giving (2x+3)(2x−3), not (2x+9)(2x−1).

257

The procedure for factoring trinomials is the easy part; the trap is using c instead of ac when a≠1. Asking "Can I find two numbers that multiply to c (or ac) and add to b?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

258

Using c instead of ac when a≠1 — the AC method needs the product a⋅c, then split the middle and group.

259

Getting the signs of p and q wrong — match signs to c (same sign if c>0, opposite if c<0) and to b.

260

Forgetting to pull a GCF first — factor out the common factor before searching for the pair, e.g. 2x2+10x+12=2(x2+5x+6).

261

The procedure for factoring by grouping is the easy part; the trap is sign error pulling the GCF from the second pair. Asking "After factoring the GCF from each pair, do both pairs leave behind the identical binomial?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

262

Sign error pulling the GCF from the second pair — when the pair is −3x−6, factor out −3 to get −3(x+2) so the binomial matches the first pair.

263

Giving up when pairs do not match — reorder the four terms (group differently) before deciding it is unfactorable.

264

Forgetting the final factor-out step — after a(c+d)+b(c+d) you must write (a+b)(c+d), not leave it half-done.

265

The procedure for simplifying radicals is the easy part; the trap is using a non-perfect-square factor. Asking "Does the number under the root have any perfect-square factor bigger than 1?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

266

Using a non-perfect-square factor — 50=2⋅25, not 5⋅10; pick the factor pair where one factor is a perfect square.

267

Distributing the root over a sum — a+b≠a+b; the product rule applies only to multiplication.

268

Leaving a perfect square inside — 72=218 is not finished; keep factoring until 72=62.

269
Radical Operations
Stuck Point

The procedure for radical operations is the easy part; the trap is adding the radicands when multiplying. Asking "For + or −, do the radicands match — and have I simplified first to check?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

270

Adding the radicands when multiplying — 2⋅3=6, not 5; multiply under one root, do not add.

271

Combining unlike radicals — 2+3 stays as is; only same-radicand terms combine.

272

Skipping simplification — 12+3 looks unlike but becomes 23+3=33 after simplifying.

273

The procedure for rationalizing denominators is the easy part; the trap is multiplying only the denominator. Asking "Is there a square root in the denominator, and is it a single term or a binomial?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

274

Multiplying only the denominator — you must multiply numerator AND denominator by the same factor to keep the value unchanged (you are multiplying by 1).

275

Using the same binomial instead of the conjugate — for 3+2 use 3−2 so the cross term cancels via difference of squares.

276

Forgetting to simplify after — 264 should reduce to 62.

277
Radical Equations
Stuck Point

The procedure for radical equations is the easy part; the trap is skipping the check. Asking "Is the unknown trapped under a radical that I undo by squaring, and did I check for extraneous roots?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

278

Skipping the check — squaring can introduce extraneous roots, so substitute every solution back into the ORIGINAL equation.

279

Squaring a sum termwise — (x+3)2=x+6x+9, not x+9; isolate the radical first to avoid this.

280

Accepting a negative result of a principal root — if isolating gives x=−2, there is no real solution since a principal root is nonnegative.

281

The procedure for simplifying rational expressions is the easy part; the trap is canceling terms instead of factors. Asking "Are the things I want to cancel FACTORS (multiplied) and not TERMS (added)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

282

Canceling terms instead of factors — x+3x does not simplify to 3; only common factors cancel, and x+3 is a sum.

283

Forgetting domain restrictions — the canceled (x−2) in x2−4x−2 still requires x≠2 in the answer.

284

Not fully factoring first — x2−9x2+6x+9 must become (x−3)(x+3)(x+3)2 before canceling.

285

The procedure for multiplying and dividing rational expressions is the easy part; the trap is flipping the wrong fraction. Asking "Are the fractions joined by × or ÷ (so I cancel and multiply across) rather than + or −?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

286

Flipping the wrong fraction — when dividing, take the reciprocal of the DIVISOR (the second fraction), not the first.

287

Multiplying before factoring — factor every numerator and denominator first so cross-cancellation simplifies the work.

288

Forgetting domain restrictions from the divisor — in division, values that make the original divisor zero are also excluded.

289

The procedure for adding and subtracting rational expressions is the easy part; the trap is adding denominators too. Asking "Do the denominators match yet — and if not, what is the LCD I must rewrite both over?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

290

Adding denominators too — ac+bc=a+bc, the denominator stays c, it does not become 2c.

291

Distributing the subtraction sign incompletely — AD−BD=A−BD requires subtracting EVERY term of B.

292

Using a denominator that is not the least common — multiplying all denominators works but creates extra simplifying; build the LCD.

293

The procedure for solving rational equations is the easy part; the trap is multiplying only some terms by the LCD. Asking "Is this an EQUATION (has =) with the variable in a denominator that I clear by the LCD and then check?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

294

Multiplying only some terms by the LCD — every term, including non-fraction ones, must be multiplied to keep the equation balanced.

295

Forgetting to check excluded values — a solved x that zeros any original denominator is extraneous and rejected.

296

Treating it like simplification — with an equals sign you clear all denominators, you do not just rewrite over the LCD.

297

The procedure for multi-step equations is the easy part; the trap is distributing only to the first term. Asking "Does isolating x take more than one step — distributing, combining, or moving variables first?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

298

Distributing only to the first term — 2(x+3)=2x+6, not 2x+3; multiply the outside number by EVERY term inside.

299

Performing inverse operations out of order — undo addition/subtraction before multiplication/division (reverse of order of operations).

300

Sign error moving a variable across — subtracting 3x from both sides of 5x=3x+8 gives 2x=8, not 8x=8.

301

The procedure for writing equations from context is the easy part; the trap is skipping the variable definition. Asking "Can I name the unknown and write two expressions that must be equal in this situation?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

302

Skipping the variable definition — write what the variable counts and include the units before building the equation.

303

Reversing subtraction or comparison language — translate from the quantity being described, not from the order of the words alone.

304

Writing an expression when the context needs an equation — look for the total, equality, or condition that completes the mathematical sentence.

305
Matrix Definition
Stuck Point

The procedure for matrix definition is the easy part; the trap is stating dimensions columns-first. Asking "Are the numbers arranged in a fixed rectangle of rows and columns with a stated size?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

306

Stating dimensions columns-first — always write m×n as rows × columns.

307

Mixing up the entry subscript order — aij is row i then column j, not the reverse.

308

Calling a non-rectangular set of numbers a matrix — every row must have the same number of entries.

309

The procedure for matrix addition, subtraction, and scalar multiplication is the easy part; the trap is adding mismatched-size matrices. Asking "For +/−, do the two matrices have exactly the same dimensions?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

310

Adding mismatched-size matrices — addition/subtraction only works when dimensions are identical.

311

Scaling only the first row or entry — a scalar multiplies EVERY entry of the matrix.

312

Confusing kA with AB — a scalar is a single number, not another matrix; do not row-by-column it.

313

The procedure for matrix multiplication is the easy part; the trap is multiplying when inner dimensions disagree. Asking "Does the column count of A equal the row count of B, and am I dotting rows with columns?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

314

Multiplying when inner dimensions disagree — (2×3)(2×2) is undefined; the inner numbers must match.

315

Assuming AB=BA — matrix multiplication is generally non-commutative, so order matters.

316

Multiplying entrywise — each result entry is a row-by-column SUM of products, not a single product.

317
Determinant
Stuck Point

The procedure for determinant is the easy part; the trap is computing ad+bc instead of ad−bc. Asking "Is the matrix square, and am I asking whether it is invertible or how it scales area?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

318
Determinant
Mistake

Computing ad+bc instead of ad−bc — the off-diagonal product is SUBTRACTED.

319
Determinant
Mistake

Trying to take a determinant of a non-square matrix — determinants exist only for square matrices.

320
Determinant
Mistake

Assuming a negative determinant means an error — a determinant can be negative; only zero means non-invertible.

321
Inverse Matrix
Stuck Point

The procedure for inverse matrix is the easy part; the trap is forgetting the 1ad−bc factor. Asking "Is the matrix square with nonzero determinant, so an undo-matrix A−1 exists?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

322

Forgetting the 1ad−bc factor — the 2×2 inverse scales the adjugate by 1/det⁡.

323

Mis-swapping entries — for 2×2, swap a and d, negate b and c: [d−b−ca].

324

Attempting to invert when det⁡=0 — a singular matrix has no inverse; check the determinant first.

325

The procedure for solving systems of equations with matrices is the easy part; the trap is using x=A−1b when det⁡A=0. Asking "Can I write the system as Ax=b and solve mechanically by row ops, inverse, or determinants?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

326

Using x=A−1b when det⁡A=0 — there is no unique solution; switch to row reduction to classify it.

327

Setting up the augmented matrix in the wrong order — align coefficients column by variable and put constants after the bar.

328

Mishandling a row operation — only swap rows, scale a row, or add a multiple of one row to another.

329

The procedure for vector addition, subtraction, and scalar multiplication is the easy part; the trap is adding magnitudes instead of components. Asking "Am I adding/subtracting matching components, or multiplying one vector by a single number?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

330

Adding magnitudes instead of components — ⟨3,0⟩+⟨0,4⟩=⟨3,4⟩, not a length of 7.

331

Scaling only one component — ku multiplies EVERY component by k.

332

Treating subtraction as commutative — u−v≠v−u; they point opposite ways.

333

The procedure for vector magnitude and direction is the easy part; the trap is adding components for length. Asking "Am I asked how long the arrow is or which way it points, rather than how to combine arrows?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

334

Adding components for length — magnitude squares, sums, then square-roots; it is not v1+v2.

335

Forgetting to normalize for a unit vector — divide the whole vector by its magnitude so the length becomes exactly 1.

336

Ignoring the quadrant for the direction angle — arctan⁡(v2/v1) may need an adjustment depending on the signs of the components.

337
Dot Product
Stuck Point

The procedure for dot product is the easy part; the trap is reporting a vector as the answer. Asking "Do I have two vectors and need one number measuring their directional agreement (not a new vector)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

338
Dot Product
Mistake

Reporting a vector as the answer - the dot product is always a single scalar; multiply matching components and add them

339
Dot Product
Mistake

Pairing components crosswise like a1b2 - pair like-with-like: a1b1+a2b2

340
Dot Product
Mistake

Forgetting that cos⁡θ form needs magnitudes - a⋅b=∥a∥∥b∥cos⁡θ, so solve cos⁡θ=a⋅b∥a∥∥b∥ for the angle

341
Cross Product
Stuck Point

The procedure for cross product is the easy part; the trap is returning a scalar. Asking "Do I have two 3D vectors and need a new vector perpendicular to both (or the area they span)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

342

Returning a scalar - the cross product is a vector; build all three components ⟨a2b3−a3b2, a3b1−a1b3, a1b2−a2b1⟩

343

Reversing the order without flipping sign - b×a=−(a×b), so order matters

344

Forgetting the middle component's sign pattern - the determinant expansion makes the j term negative; the formula already bakes this in as a3b1−a1b3

345

The procedure for algebraic manipulation is the easy part; the trap is changing only one side of an equation. Asking "Does every step keep exactly the same set of true values, just written differently?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

346

Changing only one side of an equation - whatever you do to one side you must do to the other to keep it equivalent

347

Cancelling a factor that could be zero - dividing both sides by x can delete the solution x=0; factor instead

348

Distributing a sign or exponent incorrectly - (a−b)2≠a2−b2; expand carefully so the rewrite stays equivalent

349
Linear Programming
Stuck Point

The procedure for linear programming is the easy part; the trap is searching the interior for the best value. Asking "Am I optimizing a linear objective over a region bounded by linear inequalities, with the answer expected at a corner?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

350

Searching the interior for the best value - the optimum of a linear objective lies at a vertex of the feasible region; evaluate the objective at each corner

351

Forgetting hidden constraints like x≥0 - real quantities are often nonnegative, which changes the corners

352

Mixing up maximize and minimize - read whether you want the largest or smallest objective value before comparing corners

353

The procedure for algebraic identities is the easy part; the trap is dropping the middle term: writing (a+b)2=a2+b2. Asking "Is this equality true for every value of the variable (an always-true pattern), rather than only for special values?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

354

Dropping the middle term: writing (a+b)2=a2+b2 - the perfect-square identity has 2ab: (a+b)2=a2+2ab+b2

355

Trying to 'solve' an identity for a unique value - every value satisfies it, so there is nothing to solve

356

Mismatching the sign pattern - a2−b2=(a−b)(a+b), but a2+b2 does not factor over the reals

357
Checking Solutions
Stuck Point

The procedure for checking solutions is the easy part; the trap is checking against a transformed equation instead of the original. Asking "Do I have a candidate value that I plug into the original condition to confirm both sides are equal?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

358

Checking against a transformed equation instead of the original - extraneous roots pass the squared step but fail the original; always substitute into the starting equation

359

Skipping the check after squaring or clearing denominators - these are exactly the steps that introduce false solutions

360

Evaluating only one side - compute the left and right sides separately and confirm they are equal, not just that one side computes

361
Interval Notation
Stuck Point

The procedure for interval notation is the easy part; the trap is using a bracket on infinity. Asking "Am I describing a continuous range of reals where I must mark each endpoint as included (bracket) or excluded (parenthesis)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

362

Using a bracket on infinity - ∞ and −∞ are never included, so always use a parenthesis: (−∞,3]

363

Mixing up which symbol includes - square bracket [ ] includes the endpoint (≤,≥); parenthesis ( ) excludes it (<,>)

364

Reading (2,5) as a point - in interval context it means all reals strictly between 2 and 5, not a coordinate

365
Vector Addition
Stuck Point

The procedure for vector addition is the easy part; the trap is adding the lengths instead of the components. Asking "Do I have two vectors acting together and want the single combined (resultant) vector?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

366

Adding the lengths instead of the components - ∥a∥+∥b∥ is not ∥a+b∥; add matching components first, then find the length

367

Pairing components crosswise - add x to x and y to y: ⟨a1+b1, a2+b2⟩

368

Joining the tips when the arrows are drawn tail-to-tail - the arrow from the tip of b to the tip of a is the difference a−b; for the sum, place them tip-to-tail, or tail-to-tail and take the parallelogram diagonal from the shared tail

369

The procedure for absolute value equations is the easy part; the trap is keeping only the positive case. Asking "Is an expression inside absolute-value bars set equal to a constant, asking which values are that distance away?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

370

Keeping only the positive case - ∣A∣=k means A=k or A=−k; solve both

371

Solving when the right side is negative - ∣A∣=−3 has no solution because distance can't be negative

372

Splitting before isolating the bars - first get ∣A∣ alone (e.g. ∣x∣+1=4→∣x∣=3), then split into the two cases

373

The procedure for absolute value inequalities is the easy part; the trap is treating > like <. Asking "Are absolute-value bars set < or > a value, asking for a range within or outside a distance (not an exact distance)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

374

Treating > like < - ∣A∣<k gives one interval −k<A<k, but ∣A∣>k gives two rays A<−k or A>k

375

Flipping into a sandwich for a 'greater than' - −k<A<k is the solution of ∣A∣<k, the opposite set, and k<A<−k has no solutions; for ∣A∣>k write two rays, A<−k or A>k

376

Splitting before isolating the bars - first isolate ∣A∣, then convert; e.g. ∣x∣−1<4 becomes ∣x∣<5 first

377

The procedure for graphing inequalities is the easy part; the trap is using a solid line for a strict inequality. Asking "Is the solution of a two-variable inequality a shaded region of the plane bounded by a line?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

378

Using a solid line for a strict inequality - < and > get a dashed boundary; only ≤ and ≥ get a solid one

379

Shading the wrong half-plane - pick a test point not on the line (often (0,0)); shade its side only if it makes the inequality true

380

Forgetting to shade at all - the solution is the whole half-plane region, not just the boundary line

381
Ordered Pairs
Stuck Point

The procedure for ordered pairs is the easy part; the trap is plotting up first then across. Asking "Am I naming a single point with a horizontal value first and a vertical value second?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

382

Plotting up first then across - the first number is horizontal (x), the second is vertical (y)

383

Treating (3,4) and (4,3) as the same point - order matters, so they are different locations

384

Confusing (2,5) the point with (2,5) the interval - in coordinate context it's one point, not a range of numbers

385
Simple Interest
Stuck Point

The procedure for simple interest is the easy part; the trap is compounding by accident. Asking "Is each period's interest computed on the original principal alone (so the yearly interest never changes)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

386

Compounding by accident - simple interest uses the original P every year: I=Prt, not interest on a growing balance

387

Leaving the rate as a whole percent - convert r to a decimal first (5% becomes 0.05)

388

Mismatching the time units - t is in years to match an annual rate; 6 months is t=0.5

389

The procedure for function tables and graphs is the easy part; the trap is plotting (y,x) instead of (x,y). Asking "Can I match each table row to a graph point?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

390

Plotting (y,x) instead of (x,y) — input is the horizontal coordinate.

391

Reading graph points between listed table values without checking the context — some patterns are discrete.

392

Ignoring scale on graph axes — a visually steep line may just use a different scale.