Common Mistakes in Advanced Functions

304 common pitfalls across 76 concepts, including 76 recurring stuck points

These are the pitfalls students hit across all 76 advanced functions concepts, from Function, Domain and Range 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
Function
Stuck Point

The procedure for function is the easy part; the trap is calling any equation in x and y a function. Asking "Does every allowed input give exactly one output, never two?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

2
Function
Mistake

Calling any equation in x and y a function - check first that each x gives only one y (vertical line test).

3
Function
Mistake

Thinking one output can come from only one input - functions allow many inputs to share an output; they forbid one input giving many outputs.

4
Function
Mistake

Reading f(x) as f times x - it means the output of rule f at input x.

5
Domain
Stuck Point

The procedure for domain is the easy part; the trap is listing where the function equals zero instead of where it is undefined. Asking "Which input values would make the rule undefined, and have I excluded exactly those?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

6
Domain
Mistake

Listing where the function equals zero instead of where it is undefined - the domain excludes undefined inputs, not roots.

7
Domain
Mistake

Forgetting to check both a denominator and a radical in the same problem - scan for every operation that can fail.

8
Domain
Mistake

Stating the domain as y-values - the domain is always the set of inputs (x), never outputs.

9
Range
Stuck Point

The procedure for range is the easy part; the trap is copying the domain as the range. Asking "Which output values does the function actually reach as x runs over its domain?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

10
Range
Mistake

Copying the domain as the range - inputs and outputs are different sets; compute outputs separately.

11
Range
Mistake

Forgetting outputs a rule can never produce - check for squares, absolute values, and exponentials that block negatives.

12
Range
Mistake

Reporting one peak value instead of the full set - the range is an interval or set, not a single number.

13
Inverse Function
Stuck Point

The procedure for inverse function is the easy part; the trap is reading f−1 as a reciprocal. Asking "If I know the output, does this rule hand back the exact input that produced it?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

14

Reading f−1 as a reciprocal - it means the reversing function, not 1/f.

15

Finding an inverse without checking one-to-one - if f fails the horizontal line test, no inverse exists.

16

Swapping x and y but forgetting to solve for the new y - the inverse must be expressed as output in terms of input.

17

The procedure for function composition is the easy part; the trap is applying f before g in (f∘g)(x). Asking "Is the output of one function being used as the input of another, in a fixed order?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

18

Applying f before g in (f∘g)(x) - the inner function g always goes first.

19

Multiplying outputs instead of substituting - composition plugs g(x) in for the variable in f, it does not multiply.

20

Assuming f∘g equals g∘f - order changes the result for most functions.

21

The procedure for exponential function is the easy part; the trap is putting the variable in the base instead of the exponent. Asking "Does the output multiply by the same factor for each equal step in x?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

22

Putting the variable in the base instead of the exponent - exponential means the variable is the exponent, as in bx, not xb.

23

Treating constant-percent growth as constant-amount growth - a fixed percent is exponential, a fixed amount is linear.

24

Allowing the base b to be 1 or negative - exponential requires b>0 and b≠1.

25
Logarithm
Stuck Point

The procedure for logarithm is the easy part; the trap is treating a log as division. Asking "Am I asking 'what exponent on the base gives this number?'" first is what keeps a correct-looking calculation from being attached to the wrong concept.

26
Logarithm
Mistake

Treating a log as division - log⁡b(x) is the exponent on b, not x÷b.

27
Logarithm
Mistake

Taking the log of zero or a negative number - the argument of a log must be positive.

28
Logarithm
Mistake

Confusing which way it inverts - a log frees the exponent (2x=8⇒x=log⁡28), a root frees the base.

29
Euler's Number
Stuck Point

The procedure for euler's number is the easy part; the trap is treating e as a variable to solve for. Asking "Is the growth happening continuously, with the natural base where the rate equals the amount?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

30

Treating e as a variable to solve for - it is a fixed constant, about 2.71828.

31

Using base 10 or 2 for continuously compounded growth - continuous growth uses base e.

32

Over-rounding e to 2.7 in precise work - keep enough digits (≈2.71828) for accuracy.

33

The procedure for trigonometric functions is the easy part; the trap is mixing up which sides belong to sin versus cos. Asking "Am I linking an angle to a ratio of sides (or a point on the unit circle)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

34

Mixing up which sides belong to sin versus cos - SOH-CAH-TOA: sin uses opposite, cos uses adjacent, both over hypotenuse.

35

Leaving the calculator in the wrong angle mode - match degrees or radians to the problem before computing.

36

Using right-triangle ratios for an obtuse or non-right triangle - those need the law of sines or cosines instead.

37
Periodic Functions
Stuck Point

The procedure for periodic functions is the easy part; the trap is calling a drifting or growing pattern periodic. Asking "Does the function return to the exact same value after a fixed, repeating interval?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

38

Calling a drifting or growing pattern periodic - true periodicity needs f(x+T)=f(x) with no net change per cycle.

39

Reporting a multiple of the period instead of the smallest one - the period T is the smallest positive repeat interval.

40

Confusing period with frequency - period is the time per cycle; frequency is cycles per unit, 1T.

41

The procedure for polynomial functions is the easy part; the trap is allowing negative or fractional exponents. Asking "Is every term a constant times x to a whole-number power, with only addition and subtraction joining them?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

42

Allowing negative or fractional exponents - polynomial exponents must be non-negative integers.

43

Misreading the degree from a non-leading term - the degree is the highest power, not the first written.

44

Expecting asymptotes or breaks - polynomials are smooth and defined for all real inputs.

45
Rational Functions
Stuck Point

The procedure for rational functions is the easy part; the trap is forgetting to exclude inputs where the denominator is zero. Asking "Is the function a polynomial divided by another polynomial containing the variable?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

46

Forgetting to exclude inputs where the denominator is zero - those are never in the domain.

47

Cancelling a common factor and ignoring the resulting hole - the cancelled input stays excluded as a hole.

48

Assuming a vertical asymptote wherever the denominator is zero - if the factor also cancels, it is a hole, not an asymptote.

49
Asymptote
Stuck Point

The procedure for asymptote is the easy part; the trap is believing a curve can never cross a horizontal asymptote. Asking "Is there a line the curve approaches arbitrarily closely as the input or output grows without bound?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

50
Asymptote
Mistake

Believing a curve can never cross a horizontal asymptote - it can cross horizontals; only verticals are uncrossable.

51
Asymptote
Mistake

Confusing a zero with an asymptote - a zero is where the output is 0, an asymptote is a line approached at infinity or a forbidden input.

52
Asymptote
Mistake

Reading the horizontal asymptote without comparing degrees - compare numerator and denominator degrees to find y=L.

53
Piecewise Function
Stuck Point

The procedure for piecewise function is the easy part; the trap is evaluating with the wrong piece. Asking "Does the formula used depend on which interval the input falls into?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

54

Evaluating with the wrong piece - first locate which interval the input falls in, then use only that formula.

55

Ignoring the endpoint inequality - ≤ versus < decides which piece owns a boundary value.

56

Letting intervals overlap - each input must belong to exactly one piece, or it is not a function.

57

The procedure for function transformation is the easy part; the trap is shifting the wrong direction inside the function. Asking "Is a known parent graph being moved, scaled, or flipped by added or multiplied constants?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

58

Shifting the wrong direction inside the function - f(x−3) moves right, f(x+3) moves left (opposite of the sign).

59

Confusing inside (horizontal, on x) with outside (vertical, on y) changes - a and k act on outputs, b and h on inputs.

60

Applying horizontal stretches as the literal factor - a factor b inside compresses by 1b, not by b.

61

The procedure for continuous function is the easy part; the trap is assuming defined-everywhere means continuous. Asking "Can the graph be drawn through this point without lifting the pencil?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

62

Assuming defined-everywhere means continuous - a function can have a value at every point yet still jump.

63

Overlooking holes from cancelled factors - a removable hole still breaks continuity at that point.

64

Ignoring boundary matching in piecewise functions - the pieces must agree in value at the seams to be continuous.

65

The procedure for function as mapping is the easy part; the trap is rejecting a function because two inputs share an output. Asking "Does any input point to two different outputs?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

66

Rejecting a function because two inputs share an output — repeated outputs are allowed.

67

Accepting a relation with one input and two outputs — that violates the function rule.

68

Thinking every graph is a function — use the vertical line test.

69
Input-Output View
Stuck Point

The procedure for input-output view is the easy part; the trap is letting one input map to two outputs in the box. Asking "Am I tracking what comes out for a given input, treating the rule as a sealed box?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

70

Letting one input map to two outputs in the box - a function box gives exactly one output per input.

71

Reading f(x) as multiplication - it names the box's output, not f times x.

72

Thinking you must know the inner formula to use the box - you can reason from inputs and outputs alone.

73

The procedure for multiple representations is the easy part; the trap is treating equivalent forms as different functions. Asking "Do these different-looking forms encode the exact same input-output pairs?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

74

Treating equivalent forms as different functions - check that the input-output pairs match before concluding they differ.

75

Forcing one representation everywhere - pick the view that answers the question most directly.

76

Mis-translating a verbal rule into a formula - 'three more than twice x' is 2x+3, not 3x+2 or 3(x+2).

77
One-to-One Mapping
Stuck Point

The procedure for one-to-one mapping is the easy part; the trap is confusing one-to-one with being a function. Asking "Does every output value come from at most one input?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

78

Confusing one-to-one with being a function - a function needs one output per input; one-to-one needs one input per output.

79

Using the vertical line test for one-to-one - one-to-one is checked by the horizontal line test.

80

Calling a function one-to-one when an output repeats - any repeated output value breaks it.

81

The procedure for many-to-one mapping is the easy part; the trap is calling a many-to-one function 'not a function'. Asking "Do two or more distinct inputs produce the same output?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

82

Calling a many-to-one function 'not a function' - it is valid; only one input giving two outputs is forbidden.

83

Expecting an inverse for a many-to-one function - it has none until the domain is restricted.

84

Confusing the direction - many inputs to one output is allowed; one input to many outputs is not.

85
Constant Rate
Stuck Point

The procedure for constant rate is the easy part; the trap is checking only one pair of points and declaring it constant. Asking "Does every equal step in the input add the exact same amount to the output?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

86

Checking only one pair of points and declaring it constant - test several consecutive steps for the same change.

87

Confusing equal-ratio with equal-difference - constant rate means equal differences, not a constant y/x unless it passes through zero.

88

Reading the starting value b as the rate - the rate is m, the per-unit change, not the value at x=0.

89
Changing Rate
Stuck Point

The procedure for changing rate is the easy part; the trap is reporting one average rate as 'the' rate of the function. Asking "Do equal steps in the input produce different changes in the output?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

90

Reporting one average rate as 'the' rate of the function - state the interval, because the average rate generally differs from one interval to another.

91

Confusing average rate with instantaneous rate - average uses two points; instantaneous is the limit at one point.

92

Assuming a changing rate means the function always increases - the rate can change while the function rises, falls, or both.

93

The procedure for proportional function is the easy part; the trap is calling any straight line proportional. Asking "Does input 0 give output 0, and is the ratio y/x the same for every point?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

94

Calling any straight line proportional - only lines through the origin (no +b) are proportional.

95

Taking y/x at a single point as the constant when the line has a starting value - for y=2x+3, y/x is 3.5 at x=2 but 2.5 at x=6; check that the ratio is the same at every point.

96

Forgetting to check the origin - if f(0)≠0 it cannot be proportional even if it looks linear.

97

The procedure for step function intuition is the easy part; the trap is interpolating between steps. Asking "Is the output constant within each interval and changing only by sudden jumps at boundaries?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

98

Interpolating between steps - within a step the value is constant, so a half-step input keeps the same output.

99

Mixing up floor and ceiling at thresholds - decide whether a partial unit rounds up (charged) or down (dropped).

100

Getting the boundary endpoint wrong - check whether the jump value belongs to the interval on the left or the right (open vs. closed).

101
Piecewise Behavior
Stuck Point

The procedure for piecewise behavior is the easy part; the trap is assuming continuity for free. Asking "Does the function switch to a different rule depending on which region of the domain the input is in?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

102

Assuming continuity for free - a piecewise definition can jump; check the limits at each boundary.

103

Using the wrong piece for a given input - match the input to its region before applying a rule.

104

Forgetting which piece owns the boundary point itself - the conditions (≤ vs <) decide which formula gives f(a).

105
Growth vs Decay
Stuck Point

The procedure for growth vs decay is the easy part; the trap is reading b=0.8 as growth because 0.8 is positive. Asking "Is the quantity multiplied by the same factor each period, and is that factor above or below 1?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

106

Reading b=0.8 as growth because 0.8 is positive - any base below 1 (but above 0) is decay.

107

Confusing the base with the rate - convert percents: 3% decay is b=0.97, not 0.03.

108

Treating a fixed-amount-per-period change as exponential - that's linear; exponential needs a fixed multiplier.

109
Saturation
Stuck Point

The procedure for saturation is the easy part; the trap is extrapolating early growth straight up. Asking "Does the quantity grow fast early, then slow and flatten toward a ceiling it never passes?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

110
Saturation
Mistake

Extrapolating early growth straight up - saturation means the rate falls near the limit, so the curve bends over.

111
Saturation
Mistake

Confusing the ceiling L with the final value being reached exactly - the curve approaches L asymptotically, never equaling it.

112
Saturation
Mistake

Mistaking the flattening for decay - in saturation the quantity is still rising, just ever more slowly, not shrinking.

113
Feedback
Stuck Point

The procedure for feedback is the easy part; the trap is swapping positive and negative feedback. Asking "Does the system's output get fed back in as the input for the next step?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

114
Feedback
Mistake

Swapping positive and negative feedback - positive amplifies/destabilizes, negative corrects/stabilizes.

115
Feedback
Mistake

Treating a feedback loop like a one-shot function - the rule is applied repeatedly, each output re-entering as input.

116
Feedback
Mistake

Assuming positive feedback always grows without limit - real loops often hit saturation or get checked by negative feedback.

117
Stability
Stuck Point

The procedure for stability is the easy part; the trap is confusing where the equilibrium is with whether it's stable. Asking "After a small nudge, does the system move back toward the equilibrium rather than away from it?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

118
Stability
Mistake

Confusing where the equilibrium is with whether it's stable - first solve f(x∗)=x∗, then test the slope.

119
Stability
Mistake

Using f(x∗) instead of f′(x∗) for the test - stability depends on the derivative's magnitude, not the function value.

120
Stability
Mistake

Forgetting the absolute value - ∣f′(x∗)∣<1 is stable even if f′(x∗) is negative (which adds oscillation).

121
Sensitivity
Stuck Point

The procedure for sensitivity is the easy part; the trap is calling a function 'sensitive' globally. Asking "Does a small change in the input produce a large change in the output here?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

122
Sensitivity
Mistake

Calling a function 'sensitive' globally - sensitivity is local and varies with where you measure it.

123
Sensitivity
Mistake

Confusing a large output value with high sensitivity - what matters is the change in output per small input change, not the output's size.

124
Sensitivity
Mistake

Ignoring the input scale - sensitivity is a ratio ΔfΔx, so the size of Δx matters when reporting it.

125

The procedure for local vs global behavior is the easy part; the trap is generalizing a local fact to the whole function. Asking "Is the question about the function right around one point, or about its behavior across the whole domain?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

126

Generalizing a local fact to the whole function - a tangent or approximation only describes one neighborhood.

127

Calling a local max the global max - a neighborhood high point may be beaten elsewhere on the domain.

128

Reading end behavior off a small window - global trends as x→∞ aren't visible by zooming in near one point.

129

The procedure for functional modeling is the easy part; the trap is forcing a line onto exponential data. Asking "Are you choosing and building a function to represent a real-world relationship?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

130

Forcing a line onto exponential data - check for equal ratios (exponential) vs equal differences (linear) before choosing.

131

Skipping the pattern diagnosis - identify the signature in the data before writing any equation.

132

Trusting the model far outside the data - extrapolation assumes the pattern holds, which it often doesn't.

133
Dependency Graphs
Stuck Point

The procedure for dependency graphs is the easy part; the trap is drawing the arrow toward the variable that's known first. Asking "Are you mapping which variables directly influence which others with directed arrows?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

134

Drawing the arrow toward the variable that's known first - u→v means v depends on u; the arrow points to the dependent.

135

Allowing a cycle when one isn't intended - a pure 'computes from' dependency graph should be acyclic (a DAG).

136

Confusing direct with indirect dependence - an arrow means a DIRECT influence; indirect ones come from following a path.

137
Scaling Functions
Stuck Point

The procedure for scaling functions is the easy part; the trap is applying the horizontal rule like the vertical one. Asking "Is the function the same shape multiplied by a constant on the output or input (not shifted)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

138

Applying the horizontal rule like the vertical one - f(2x) compresses (factor 12), it does not stretch.

139

Confusing amplitude (vertical) with period (horizontal) - c f(x) changes amplitude; f(cx) changes period.

140

Forgetting a negative multiplier also reflects - ∣c∣ scales while the sign of c flips the graph.

141
Shifting Functions
Stuck Point

The procedure for shifting functions is the easy part; the trap is reading f(x−3) as a left shift. Asking "Is the graph the same shape just moved by an added constant (not stretched or flipped)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

142

Reading f(x−3) as a left shift - inside shifts reverse: x−3 moves the graph RIGHT 3.

143

Mixing up inside and outside constants - inside affects horizontal, outside affects vertical.

144

Thinking a shift changes the shape - translation only moves position; size and orientation are untouched.

145

The procedure for reflecting functions is the easy part; the trap is swapping which negative flips which axis. Asking "Is the graph a mirror image of the parent caused by a negative sign (not a slide or a stretch)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

146

Swapping which negative flips which axis - outside −f(x) is the x-axis flip; inside f(−x) is the y-axis flip.

147

Calling y=x2 asymmetric - it's even, equal to its own y-axis reflection.

148

Confusing a reflection with a rotation - a flip mirrors across a line; it does not rotate the graph.

149
Composition Chains
Stuck Point

The procedure for composition chains is the easy part; the trap is evaluating left to right. Asking "Is one function's output being fed as the input to the next in a fixed order?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

150

Evaluating left to right - composition is inside-out; the rightmost (innermost) function runs first.

151

Assuming f∘g=g∘f - composition is generally not commutative; order changes the result.

152

Plugging the input into the wrong stage - feed x into the innermost function, then pass each result outward.

153
Function Families
Stuck Point

The procedure for function families is the easy part; the trap is treating m and b as variables. Asking "Do these functions all share one general form, differing only in the values of their constants?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

154

Treating m and b as variables - parameters are fixed for one member; only x and y vary.

155

Mixing members of different families - y=mx+b and y=ax2 aren't the same family; the general FORM must match.

156

Forgetting the parent - every transformed function is a member of a family with a baseline parent shape.

157

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

158

Assuming all features are invariant - shifts change intercepts, scales change amplitude; only some properties survive.

159

Confusing invariance with symmetry - symmetry is a function being its own image; invariance is a property being preserved.

160

Naming the wrong feature - check the specific property against the specific transformation before claiming it's invariant.

161
Unit Circle
Stuck Point

The procedure for unit circle is the easy part; the trap is swapping sin⁡ and cos⁡ in the coordinates. Asking "Are you reading sine and cosine of an angle as coordinates on a circle of radius 1?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

162
Unit Circle
Mistake

Swapping sin⁡ and cos⁡ in the coordinates - x=cos⁡θ, y=sin⁡θ, in that order.

163
Unit Circle
Mistake

Forgetting the sign by quadrant - cosine is negative in quadrants II and III, sine negative in III and IV.

164
Unit Circle
Mistake

Assuming the radius scaling - only on the UNIT circle do coordinates equal (cos⁡θ,sin⁡θ) directly; a radius-r circle needs a factor of r.

165
Radian Measure
Stuck Point

The procedure for radian measure is the easy part; the trap is plugging a degree value into a calculator set to radians. Asking "Is the angle measured by arc-lengths-of-radius around the circle rather than by a slice of 360?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

166

Plugging a degree value into a calculator set to radians - match the calculator mode to the unit you actually have.

167

Forgetting the unitless π180 only converts degrees to radians, not the reverse - multiply by 180π to go back to degrees.

168

Treating 1 radian as a 'nice' round angle - it is about 57.3°, not 60°, so estimates drift.

169

The procedure for trigonometric function graphs is the easy part; the trap is using b directly as the period. Asking "Is the curve a repeating wave whose height, repeat length, and center I can name from a, b, c, d?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

170

Using b directly as the period - the period is 2π∣b∣, so divide.

171

Forgetting to factor b out before reading the phase shift - the shift is cb, not c.

172

Letting a negative a change the amplitude - amplitude is ∣a∣; the negative only flips the wave.

173

The procedure for inverse trigonometric functions is the easy part; the trap is treating sin⁡−1 as 1sin⁡. Asking "Am I starting from a ratio and asking for the angle, with the answer pinned to one restricted range?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

174

Treating sin⁡−1 as 1sin⁡ - the −1 superscript means inverse function, and reciprocal is csc⁡.

175

Reporting an angle outside the principal range - arcsin⁡ returns only [−π2,π2], arccos⁡ only [0,π].

176

Assuming arcsin⁡(sin⁡θ)=θ for every θ - it only holds when θ is already in the restricted domain.

177

The procedure for pythagorean trigonometric identities is the easy part; the trap is reading sin⁡2θ as sin⁡(θ2). Asking "Do I have squared trig functions I can collapse to 1 or swap using the unit-circle relation?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

178

Reading sin⁡2θ as sin⁡(θ2) - it means (sin⁡θ)2, sine first then square.

179

Misremembering the derived forms - divide sin⁡2+cos⁡2=1 by cos⁡2 to get 1+tan⁡2=sec⁡2, not tan⁡2=sec⁡2.

180

Setting the sum equal to the angle - sin⁡2θ+cos⁡2θ is always 1, independent of θ.

181

The procedure for sum and difference identities is the easy part; the trap is splitting cos⁡(A+B) as cos⁡A+cos⁡B. Asking "Is the argument of the trig function a sum or difference of two angles I want to break apart?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

182

Splitting cos⁡(A+B) as cos⁡A+cos⁡B - it expands to cos⁡Acos⁡B−sin⁡Asin⁡B, a product mix.

183

Getting the cosine sign wrong - in cosine the inside + becomes a − between the products (∓ flips).

184

Using matching signs for cosine - sine and tangent keep the sign, cosine reverses it.

185

The procedure for double-angle identities is the easy part; the trap is writing sin⁡2θ=2sin⁡θ. Asking "Is the angle exactly twice another, so I can express it from single-angle trig values?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

186

Writing sin⁡2θ=2sin⁡θ - it is 2sin⁡θcos⁡θ, the sum identity with equal angles.

187

Picking the wrong cos⁡2θ form - use 1−2sin⁡2θ when you only know sine, 2cos⁡2θ−1 when you only know cosine.

188

Doubling the function for cosine too - cos⁡2θ≠2cos⁡θ; it equals cos⁡2θ−sin⁡2θ.

189

The procedure for logarithm properties is the easy part; the trap is turning log⁡(x+y) into log⁡x+log⁡y. Asking "Is the log's argument a product, quotient, or power I can split into add, subtract, or a front multiplier?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

190

Turning log⁡(x+y) into log⁡x+log⁡y - the sum rule applies to products log⁡(xy), never sums.

191

Leaving the exponent in place - the power rule pulls n out front as nlog⁡bx.

192

Reversing quotient and product - division gives subtraction, multiplication gives addition.

193
Natural Logarithm
Stuck Point

The procedure for natural logarithm is the easy part; the trap is treating ln⁡ as base 10. Asking "Is the base e (continuous growth), so the inverse I want is ln⁡ rather than a base-10 log?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

194

Treating ln⁡ as base 10 - ln⁡ is base e; the base-10 log is written log⁡.

195

Forgetting ln⁡e=1 and ln⁡1=0 - the log of the base is 1, the log of 1 is 0.

196

Not using ln⁡ and ex as inverses - eln⁡x=x and ln⁡(ex)=x cancel directly.

197

The procedure for change of base formula is the easy part; the trap is flipping the ratio. Asking "Is the base something other than e or 10 that I must turn into a computable ratio of logs?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

198

Flipping the ratio - it is log⁡xlog⁡b (target over base), not base over target.

199

Switching intermediate bases mid-problem - use the same base a in numerator and denominator.

200

Thinking the new base must be 10 or e - any base works; those two are just the ones on the calculator.

201

The procedure for solving exponential equations is the easy part; the trap is dividing instead of taking a log. Asking "Is the unknown stuck up in the exponent, so I need a logarithm to bring it down?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

202

Dividing instead of taking a log - an exponent comes down only via a logarithm, never division.

203

Forgetting the power rule after taking the log - rewrite ln⁡(ax) as xln⁡a to expose x.

204

Confusing it with a log equation - here the variable is the exponent, so you take a log, not exponentiate.

205

The procedure for solving logarithmic equations is the easy part; the trap is skipping the domain check. Asking "Is the unknown the argument of a log, so I rewrite as bc=argument to release it?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

206

Skipping the domain check - reject any solution that makes a log's argument zero or negative.

207

Converting before combining - merge multiple logs into one with the properties, then exponentiate.

208

Mixing up direction - the variable is inside the log, so exponentiate; do not take another log.

209

The procedure for equation of a circle is the easy part; the trap is reading the center sign backwards. Asking "Are x2 and y2 present with equal positive coefficients and a constant on the other side?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

210

Reading the center sign backwards - (x−h) gives center +h, so (x+2)2 means center at −2.

211

Forgetting to square-root the right side - the equation gives r2, so radius is r2.

212

Treating it as an ellipse - a circle requires equal coefficients on x2 and y2.

213
Ellipse
Stuck Point

The procedure for ellipse is the easy part; the trap is using a2+b2 for the foci. Asking "Are both squared terms positive, added, with different denominators equaling 1?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

214
Ellipse
Mistake

Using a2+b2 for the foci - an ellipse uses c2=a2−b2; the plus version is for hyperbolas.

215
Ellipse
Mistake

Assuming a is always under x - the major axis lies under the LARGER denominator, which may be y.

216
Ellipse
Mistake

Confusing it with a circle - unequal denominators mean an ellipse, not a circle.

217
Hyperbola
Stuck Point

The procedure for hyperbola is the easy part; the trap is using a2−b2 for the foci. Asking "Is one squared term subtracted from the other (opposite signs) with the result equaling 1?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

218
Hyperbola
Mistake

Using a2−b2 for the foci - a hyperbola adds: c2=a2+b2.

219
Hyperbola
Mistake

Reading the opening direction wrong - the branch opens along the variable of the POSITIVE term.

220
Hyperbola
Mistake

Mistaking the larger denominator for a2 - in a hyperbola a2 sits under the positive term regardless of size.

221

The procedure for parabola (focus-directrix definition) is the easy part; the trap is equating p with the coefficient a. Asking "Is the curve the set of points equally far from a single point and a single line, with only one variable squared?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

222

Equating p with the coefficient a - convert via 4p=1a; p is the vertex-to-focus distance.

223

Putting focus and directrix on the same side of the vertex - they sit opposite, each a distance ∣p∣ away.

224

Expecting two squared terms - a parabola has exactly one variable squared.

225

The procedure for conic sections overview is the easy part; the trap is reading B2−4AC as a root count. Asking "Am I deciding the TYPE of conic from a general equation rather than analyzing one specific known conic?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

226

Reading B2−4AC as a root count - its SIGN names the conic type, not the number of solutions.

227

Ignoring the A=C,B=0 refinement - a negative discriminant is an ellipse, or a circle if also A=C and B=0.

228

Skipping classification - identify the conic first, then pull the matching standard form.

229
Polar Coordinates
Stuck Point

The procedure for polar coordinates is the easy part; the trap is reading (r,θ) as (x,y). Asking "Is the location given as a distance from the origin plus an angle, rather than horizontal and vertical amounts?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

230

Reading (r,θ) as (x,y) - the first number is a distance, the second an angle.

231

Mishandling the angle's quadrant in θ=arctan⁡(y/x) - arctan alone can land in the wrong quadrant; check the signs of x and y.

232

Forgetting a point has many polar names - adding 2π to θ (or negating r and adding π) gives the same point.

233
Polar Graphs
Stuck Point

The procedure for polar graphs is the easy part; the trap is miscounting rose petals. Asking "Is the equation r expressed in terms of θ, traced by sweeping the angle around?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

234
Polar Graphs
Mistake

Miscounting rose petals - odd n gives n petals, even n gives 2n.

235
Polar Graphs
Mistake

Plotting (r,θ) as (x,θ) on a square grid - use the polar grid of concentric circles and radial lines.

236
Polar Graphs
Mistake

Ignoring negative r - when r<0 the point is plotted in the opposite direction, completing many curves.

237

The procedure for parametric equations is the easy part; the trap is believing eliminating t keeps everything. Asking "Are x and y each written as a function of a separate parameter that drives both together?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

238

Believing eliminating t keeps everything - the resulting xy-equation drops direction and speed.

239

Forcing the curve to be a function - parametric paths can loop or cross, failing the vertical-line test.

240

Treating t as x - t is an independent clock that drives both x and y, not the horizontal axis.

241
Parametric Graphs
Stuck Point

The procedure for parametric graphs is the easy part; the trap is connecting points by x order. Asking "Am I sketching or analyzing the actual traced path of (x(t),y(t)), including its direction or tangent?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

242

Connecting points by x order - join them in increasing-t order, since the path can reverse.

243

Taking dydx as dx/dtdy/dt - it is dy/dtdx/dt, the y-rate over the x-rate.

244

Ignoring direction arrows after eliminating t - the Cartesian shape hides which way the curve is traced.

245
Compound Interest
Stuck Point

The procedure for compound interest is the easy part; the trap is using the annual rate r directly when compounding more than once a year. Asking "Does each period's interest get added to the balance so the next period earns on a larger amount?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

246

Using the annual rate r directly when compounding more than once a year - divide by n to get the periodic rate r/n and use exponent nt.

247

Forgetting to convert the percent to a decimal - 6% enters the formula as 0.06, not 6.

248

Treating compound interest like simple interest by multiplying - you must raise (1+r/n) to the nt power, not multiply principal by rate by time.

249
Annuities
Stuck Point

The procedure for annuities is the easy part; the trap is using the annual rate as i. Asking "Is the same amount paid repeatedly at fixed intervals, rather than once?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

250
Annuities
Mistake

Using the annual rate as i - the periodic rate i is the annual rate divided by payments per year (e.g. 6% monthly gives i=0.005).

251
Annuities
Mistake

Confusing n with years - n is the TOTAL number of payments (months × years for monthly), not the number of years.

252
Annuities
Mistake

Mixing up future-value and present-value forms - use (1+i)n−1i to find what deposits grow to, and 1−(1+i)−ni to find what a future stream is worth now.

253

The procedure for present and future value is the easy part; the trap is discounting when you meant to grow (or vice versa). Asking "Am I moving one sum of money forward (growing) or backward (discounting) along the timeline?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

254

Discounting when you meant to grow (or vice versa) - dividing by (1+r)t moves money BACK to today, multiplying moves it forward.

255

Comparing future and present amounts directly without converting - bring both to the same point in time before judging which is larger.

256

Using the wrong sign or direction in NPV - the initial cost at t=0 is divided by (1+r)0=1 and is usually negative.

257
Lines in 3D
Stuck Point

The procedure for lines in 3d is the easy part; the trap is confusing the point with the direction vector. Asking "Does the line live in x,y,z space and need a direction vector rather than a single slope?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

258
Lines in 3D
Mistake

Confusing the point with the direction vector - (x0,y0,z0) is where the line is, ⟨a,b,c⟩ is which way it goes; they play different roles.

259
Lines in 3D
Mistake

Writing symmetric form when a direction component is zero - if a=0 you cannot divide by it, so keep that coordinate as a separate equation like x=x0.

260
Lines in 3D
Mistake

Assuming two lines with different direction vectors must cross - in 3D they can be skew (never meet and never parallel).

261
Planes in 3D
Stuck Point

The procedure for planes in 3d is the easy part; the trap is using a direction vector instead of the normal vector. Asking "Is the object a flat surface fixed by a perpendicular (normal) vector and one equation ax+by+cz=d?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

262
Planes in 3D
Mistake

Using a direction vector instead of the normal vector - a plane is built from the vector PERPENDICULAR to it, not one lying in it.

263
Planes in 3D
Mistake

Reading the coefficients wrong - in ax+by+cz=d the normal is ⟨a,b,c⟩ (the coefficients), and d alone does not affect orientation, only position.

264
Planes in 3D
Mistake

Forgetting the absolute value or the a2+b2+c2 in the distance formula - distance is always nonnegative and divided by the normal's length.

265
Function Notation
Stuck Point

The procedure for function notation is the easy part; the trap is reading f(x) as f times x. Asking "Are the parentheses holding an input to a named function (not a multiplication)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

266

Reading f(x) as f times x - the parentheses hold the input; multiplication never happens here.

267

Substituting only part of a compound input - in f(x+2) replace every x in the rule with the whole expression (x+2).

268

Confusing the input with the output - in f(3)=10, the 3 goes in (input) and the 10 comes out (output), not the reverse.

269

The procedure for symmetric functions is the easy part; the trap is judging symmetry from a rough sketch instead of algebra. Asking "When you replace x with −x, do you get back f(x) (even), −f(x) (odd), or neither?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

270

Judging symmetry from a rough sketch instead of algebra - substitute −x and compare; a picture can mislead.

271

Assuming a function must be even or odd - many are neither, so the test can come back 'no symmetry.'

272

Forgetting to distribute the negative through powers - (−x)3=−x3 but (−x)2=+x2; sign behavior depends on the exponent.

273
Restricted Domain
Stuck Point

The procedure for restricted domain is the easy part; the trap is restricting to an interval where the property still fails. Asking "Am I deliberately limiting the inputs so the function gains a property (like passing the horizontal line test)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

274

Restricting to an interval where the property still fails - check that the chosen interval truly makes outputs unique (passes the horizontal line test).

275

Confusing the natural domain with a restricted one - the natural domain is forced by the rule; a restriction is a deliberate extra choice.

276

Forgetting the restriction carries into the inverse - the restricted domain becomes the inverse function's range, which is why x≥0 only.

277

The procedure for horizontal line test is the easy part; the trap is using vertical lines instead of horizontal. Asking "Does every horizontal line cross the graph at most once?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

278

Using vertical lines instead of horizontal - vertical lines test 'is it a function,' horizontal lines test 'is it one-to-one.'

279

Declaring a function has no inverse forever - it fails on its full domain but can pass after a domain restriction.

280

Misreading 'at most once' as 'exactly once' - a horizontal line may miss the graph entirely; what matters is that it never hits twice.

281
Amplitude
Stuck Point

The procedure for amplitude is the easy part; the trap is using the full crest-to-trough height as amplitude. Asking "Am I measuring the vertical distance from the midline to a peak (half the total swing)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

282
Amplitude
Mistake

Using the full crest-to-trough height as amplitude - amplitude is half that: ymax−ymin2.

283
Amplitude
Mistake

Taking A as signed when it can be negative - amplitude is ∣A∣, always nonnegative.

284
Amplitude
Mistake

Confusing amplitude with period - amplitude is vertical (height), period is horizontal (cycle length).

285
Frequency
Stuck Point

The procedure for frequency is the easy part; the trap is reporting frequency as the period. Asking "Am I counting how many complete cycles happen per unit (not the length of one cycle or its height)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

286
Frequency
Mistake

Reporting frequency as the period - they are reciprocals, so f=1/T, never equal unless T=1.

287
Frequency
Mistake

Confusing frequency with amplitude - frequency is how often it repeats, amplitude is how tall it is.

288
Frequency
Mistake

Mixing frequency f with angular frequency B - the coefficient inside the sine is B=2πf, not f itself.

289
Parent Functions
Stuck Point

The procedure for parent functions is the easy part; the trap is treating a shifted/stretched graph as a new family. Asking "Is this the simplest untransformed template that all others in the family are built from?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

290

Treating a shifted/stretched graph as a new family - peel off the transformations to find the underlying parent.

291

Forgetting the parent's own domain and range - x starts at x≥0, so its transformations inherit that restriction.

292

Mixing up parent shapes - x2 is a U, ∣x∣ is a sharp V, x3 is an S; learn the distinct templates.

293
Exponential Growth
Stuck Point

The procedure for exponential growth is the easy part; the trap is modeling percent growth as linear (adding a fixed amount). Asking "Is the quantity multiplied by the same factor each period (rather than having a fixed amount added)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

294

Modeling percent growth as linear (adding a fixed amount) - growth by a rate is multiplication by (1+r), so use a power, not a slope.

295

Adding the rate instead of using (1+r) - 5% growth multiplies by 1.05 each period, not adds 0.05.

296

Confusing the growth factor with the rate - in (1+r)t, r=0.05 but the multiplier each step is 1.05.

297

The procedure for even and odd functions is the easy part; the trap is assuming 'not even' means 'odd'. Asking "Does f(−x) equal f(x) (even), equal −f(x) (odd), or neither?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

298

Assuming 'not even' means 'odd' - run both tests; a function can be neither.

299

Sign-handling powers wrong - (−x)2=x2 (an even power cancels the negative sign) but (−x)3=−x3 (an odd power keeps it).

300

Eyeballing symmetry from a sketch - confirm algebraically by substituting −x, not by visual guess.

301
Radians
Stuck Point

The procedure for radians is the easy part; the trap is leaving the calculator in degree mode for radian work (or vice versa). Asking "Is the angle measured by arc-length-over-radius (so a full circle is 2π, not 360)?" first is what keeps a correct-looking calculation from being attached to the wrong concept.

302
Radians
Mistake

Leaving the calculator in degree mode for radian work (or vice versa) - match the mode to the unit before computing a trig value.

303
Radians
Mistake

Converting wrong - multiply degrees by π180 to get radians, by 180π to go back.

304
Radians
Mistake

Treating θ=s/r as having units of length - the radius cancels, so radians are dimensionless (a pure ratio).