Linear Inequalities & Graphs — 700-800 - Complete Interactive Lesson
Part 1: The 700-800 Patterns
The 700-800 Patterns: Linear Inequalities & Graphs
Part 1 of 3 — Constraint Systems Under Pressure
Hard-tier inequality items are optimization problems in disguise: multiple constraints, and the answer lives at whichever constraint binds first.
Archetype 1: The Binding Constraint
When two resources limit production (beads AND clasps, rods AND sheets), compute the limit each imposes separately — the smaller limit wins. The larger limit is always an option.
Worked example. Each birdhouse needs boards and screws; boards and screws available. Max birdhouses?
Boards: . Screws: . The screws bind: . An item may then ask for revenue at \2022 \times 20 = $44024 \times 20 = $48022$ as options.
Archetype 2: Substitute the Known Coordinate, Combine the Bounds
Given a system like and with a point : substitute into BOTH inequalities to get a bound from each, then take the tighter one. Strict inequalities exclude their boundary — "greatest integer " with is , not .
Worked example. satisfies and . Least integer ?
First: , so . Second: , so . Both must hold — the stricter bound governs: . Using only one inequality gives , the planted trap.
Archetype 3: Requirements Plus a Budget (Round the Right Way)
Real-world systems mix a minimum requirement ("at least 40 chairs", "at least $170 earned") with a cap (budget, total hours). Fund the requirement first, then see what's left — and round DOWN for capacity, UP for requirements.
Worked example. Chairs \1240$45$1{,}500$. Max tables?
Chairs claim 40 \times 12 = \480$1{,}0201020 \div 45 = 22.67 \rightarrow223323$ — both are in the options.
Part 2: Traps & Speed
Traps & Speed: Linear Inequalities & Graphs
Part 2 of 3 — Boundary Games and Test-Point Discipline
The Boundary Is Where They Get You
Nearly every hard inequality distractor is a boundary story:
- Strict boundary planted as an answer. If , a point giving exactly FAILS — but it will be an option, and it will pass the other inequality convincingly.
- Round-up on a budget / round-down on a requirement. Both wrong directions always appear. Budget: . Requirement: .
- The ignored constraint. Answers computed from only one of the two (or three) conditions are systematically planted — usually as the LARGER, more satisfying number.
- Least vs. greatest. After combining bounds like , the test asks for one end and offers both.
Test-Point Discipline (the 20-second method)
For "which ordered pair is a solution" items, don't graph — test each option in the harder inequality first (the one more options will fail). Eliminate, then run survivors through the second inequality. Check strict vs. non-strict on EVERY substitution that lands exactly on a boundary; the test engineers one option to land there on purpose.
Desmos Exploits
- Type both inequalities directly (Desmos shades them); the solution region is the overlap. Then check options by clicking — or plot each option as a point and see which lands in the dark region. Points on a dashed boundary don't count; on a solid boundary they do.
- For "greatest integer such that works": add the vertical line and read off where it crosses the shaded overlap.
- Word problems: translating to a system and letting Desmos shade is usually SLOWER than funding the requirement first and dividing the leftover. Save Desmos for genuinely two-dimensional questions.
Part 3: Timed Drill
Timed Drill: Linear Inequalities & Graphs
Part 3 of 3 — Four Questions, Full Difficulty
Target pace: 75 seconds per question.
Pre-flight checklist:
- Count the constraints. Every one of them must be used or consciously ruled out.
- Requirement round up. Budget/capacity round down. Say it before you round.
- Strict inequality the boundary itself is OUT.
Start the clock.