Quadratics: A Practical Course with Mateo Alvarez

Start with the purpose

Place Quadratics inside a worked problem where the setup matters as much as the answer. Name the result a learner is trying to produce and the constraints that make the skill useful.

How Quadratics actually works

These are the load-bearing ideas. Everything later in the course is an application of one of them, so it is worth reading slowly and returning to when something stops making sense.

• The discriminant predicts the roots. For ax² + bx + c = 0 the discriminant D = b² - 4ac settles the answer type before you solve: D > 0 gives two distinct real roots, D = 0 gives one repeated root, D < 0 gives two complex conjugate roots. Computing D first tells you what to expect and catches sign slips early.
• Vieta gives a free check. For any quadratic the sum of the roots equals -b/a and their product equals c/a. After solving, add and multiply your two answers; if they do not match those ratios, an error sits somewhere in the working.
• Completing the square finds the vertex. Rewriting ax² + bx + c in the form a(x + b/(2a))² + k puts the vertex at x = -b/(2a). That x value is the axis of symmetry and marks the minimum when a > 0 or the maximum when a < 0.

Misconceptions worth clearing early

Each of these is common, understandable, and expensive to leave in place. Recognising them now saves rework later.

• Dropping the sign of b when squaring it. Learners read b = -7 and write b² as -49 instead of 49. Fix: Put b in brackets every time: (-7)² = 49, whereas -7² evaluates to -49.
• Dividing only the radical by 2a. The formula is often mis-remembered as -b plus the root over 2a, with the -b left outside. Fix: Keep the entire numerator over one fraction bar, so both -b and the square root are divided by 2a.
• Sign errors when rearranging. Moving several terms in one written step hides the operation being applied. Fix: Apply one operation to both sides at a time and write the step down, even when it feels obvious.

Build the mental model

Connect the key terms as a process rather than a word list. Use this sequence: represent the information, choose a method, calculate carefully, and verify the result.

Catch the common miss

Compare a surface-level attempt with one that shows a correct setup, visible steps, checked units or assumptions, and a clear interpretation. Explain the single difference that matters most.

Watch the whole process

Trace a model from the initial prompt to a worked solution set with a reasoning note. Mark each point where the learner must observe, choose, or verify rather than act automatically.

Worked example: Locating the turning points of f(x) = x³ - 6x² + 9x

Follow each step and predict the next before you read it. Predicting first is what turns a demonstration into practice.

1. Differentiate to get f'(x) = 3x² - 12x + 9, which factors as 3(x - 1)(x - 3).
2. Set the derivative to zero, giving critical points at x = 1 and x = 3.
3. Take the second derivative, 6x - 12. At x = 1 it is -6, which is negative, so x = 1 is a local maximum.
4. At x = 3 the second derivative is +6, so x = 3 is a local minimum. The function values are 4 and 0 respectively.

The sign of the second derivative classifies a critical point outright, with no plotting or testing of nearby values needed.

Where this usually goes wrong

Watch for these while you work through the demonstration rather than afterwards.

• Differentiating a product term by term. Sums do differentiate term by term, so learners assume products behave the same way. Fix: Use the product rule: the derivative of uv is u'v + uv'. Test the shortcut on x times x, whose derivative is 2x rather than 1.
• Leaving out the constant of integration. An indefinite integral feels finished the moment an antiderivative appears. Fix: Always append + C. It becomes load-bearing as soon as you solve a differential equation with an initial condition.
• Sign errors when rearranging. Moving several terms in one written step hides the operation being applied. Fix: Apply one operation to both sides at a time and write the step down, even when it feels obvious.

Practice with scaffolding

Repeat the model with one detail changed. Keep the prompts visible and say or write the reason for each choice before continuing.

Check before feedback

Use a correct setup, visible steps, checked units or assumptions, and a clear interpretation as the quality test. Make one self-correction before asking the tutor to review the result.

Read the situation

Translate the scenario into a clear task. Separate facts, assumptions, constraints, and information that is interesting but not relevant to Newtonian mechanics.

Choosing well under real constraints

Applied work is mostly judgement under limits: less time, less information, and more competing goals than a textbook example allows. These are the decision rules that hold up in practice.

• Several methods could solve the problem: Choose the one whose setup you can state clearly; a slower method you understand beats a faster one you half-recall.
• You are stuck at the setup: Solve a smaller version with easy numbers first, then generalise the structure you used.
• The answer looks wrong but the arithmetic checks out: Recheck the translation from words to symbols; the error is usually upstream of the calculation.

Reading the situation before acting

Before choosing an approach, state three things explicitly: what result the situation actually requires, which constraints are fixed rather than preferences, and what evidence would tell you the approach is working. Skipping this step is the most common reason competent work solves the wrong problem.

• Newton's second law concerns net force. F = ma refers to the vector sum of every force acting on a body, not to any single applied force. A car cruising at constant speed has zero net force on it, which is why the engine must keep running just to cancel drag and rolling resistance.

Practitioner notes

Small pieces of working knowledge that rarely appear in introductory material.

• Draw the free-body diagram and label your positive direction before writing a single equation. Most sign errors are locked in at that moment, not during the algebra.
• Check magnitude and units at the end. A household-strength push producing 400 m/s² means a mass or a decimal point went astray.

Compare real options

Generate two workable approaches and test both against the purpose. Do not hide the tradeoff; name what each option improves and what it gives up.

Make the reasoning visible

Produce a worked solution set with a reasoning note and attach a short decision note. The note should make the result auditable, not merely confident.

Use the rubric, not a feeling

Review the work for a correct setup, visible steps, checked units or assumptions, and a clear interpretation. Record evidence for each judgment so feedback points to something observable.

Diagnostic checklist

Run this before you revise anything. Diagnosing first prevents the common failure of polishing the parts that were already fine.

• Check: Dropping the sign of b when squaring it — is this present in your work?
• Check: Dividing only the radical by 2a — is this present in your work?
• Check: Sign errors when rearranging — is this present in your work?
• Check: Dropping or mixing units — is this present in your work?

The quality bar

This is what finished work looks like in this field. Use it as the standard for your revision rather than a general sense of improvement.

• The setup states what each symbol means, including units
• Steps are visible enough for a reader to find the exact point of any disagreement
• The result is checked against the original problem and interpreted in context

Diagnose before editing

Name the symptom, then ask what decision or missing step produced it. Choose the cause you can address rather than changing everything at once.

Revise and compare

Make one purposeful revision and compare the two versions. Keep the change only if it improves the intended result without creating a larger problem.

Define a finishable brief

Choose a specific audience, result, and boundary for the Unit conversion capstone. Reduce scope until the project can be finished and reviewed in one focused cycle.

Bringing the parts together

A capstone is judged on coherence, not on the number of techniques it includes. Return to the core ideas and make sure the work demonstrates them rather than decorating them.

• A conversion factor is a fraction equal to one. Because 1 inch equals 2.54 cm exactly, the ratio of 2.54 cm to 1 inch has a value of one and can multiply any quantity without changing it. Orient the fraction so the unwanted unit cancels, and the cancellation itself confirms the setup.
• SI prefixes are powers of ten. Each prefix is a fixed power: kilo is a thousand, centi is a hundredth, milli is a thousandth, micro is a millionth. Converting between prefixes only ever shifts the decimal point, so any answer that changes by something other than a power of ten is wrong.
• Derived units convert component by component. A unit such as metres per second or grams per cubic centimetre needs each part converted separately, and squared or cubed units need the linear factor raised to the same power. One square metre is 10,000 square centimetres, and one cubic metre is a million cubic centimetres.

Standards that make the work credible

These are the marks of work that would be taken seriously by someone who does this professionally.

• The setup states what each symbol means, including units
• Steps are visible enough for a reader to find the exact point of any disagreement
• The result is checked against the original problem and interpreted in context

Practitioner notes

Small pieces of working knowledge that rarely appear in introductory material.

• Sanity check direction against magnitude. Converting into a smaller unit must produce a bigger number, so 5 km expressed in metres has to come out larger than 5.
• Carry units in code as carefully as on paper. NASA lost the Mars Climate Orbiter in 1999 because thruster impulse was supplied in pound-force seconds while the navigation software expected newton-seconds.

Build with checkpoints

Plan foundation, first draft, verification, and revision milestones. At each checkpoint, save evidence instead of relying on memory.

Present and continue

Present a worked solution set with a reasoning note with a concise rationale. Use the final rubric to choose one strength to retain and one next practice target.