Teaching Algorithms Across Disciplines in Grades 9-10 (Level 1): Oklahoma Standard L1.IC.CU.03 Teaching algorithms across disciplines in grades 9-10 (level 1) does not have to be complicated. Picture a bioinformatics technician adapting a search algorithm from text search to genetic sequence matching. That kind of thinking is exactly what Oklahoma's grades 9-10 (level 1) computer…
Teaching Comparing Data Structures in Grades 11-12 (Level 2): Oklahoma Standard L2.AP.V.01 Teaching stacks and queues in grades 11-12 (level 2) does not have to be complicated. Picture a backend engineer choosing a queue to fairly process thousands of incoming server requests without dropping any. That kind of thinking is exactly what Oklahoma's grades 11-12…
Teaching Modifying Existing Programs in Grades 11-12 (Level 2): Oklahoma Standard L2.AP.PD.07 Teaching modifying computer programs in grades 11-12 (level 2) does not have to be complicated. Picture a software engineer adding a feature to production code while running regression tests to confirm nothing else broke. That kind of thinking is exactly what Oklahoma's grades…
Teaching Explaining Security Issues in Programs in Grades 11-12 (Level 2): Oklahoma Standard L2.AP.PD.06 Teaching cybersecurity vulnerabilities in grades 11-12 (level 2) does not have to be complicated. Picture a security analyst writing a vulnerability report that names the exact flawed design choice and what an attacker could gain from it. That kind of thinking…
Teaching Proving It Works: Designing Test Cases in Grades 11-12 (Level 2): Oklahoma Standard L2.AP.PD.05 Teaching software test cases in grades 11-12 (level 2) does not have to be complicated. Picture a QA engineer writing a structured test plan covering typical, boundary, and invalid inputs before a release is approved. That kind of thinking is…
Teaching Systematic Code Review in Grades 11-12 (Level 2): Oklahoma Standard L2.AP.PD.04 Teaching code review checklist in grades 11-12 (level 2) does not have to be complicated. Picture a software engineer reviewing a teammate's pull request against a six-criteria checklist before approving it for the shared codebase. That kind of thinking is exactly what Oklahoma's…
Teaching Working Like a Dev Team in Grades 11-12 (Level 2): Oklahoma Standard L2.AP.PD.02 Teaching version control for teams in grades 11-12 (level 2) does not have to be complicated. Picture a software engineer opening a pull request and waiting for teammate code review before merging a new feature into the main branch. That kind…
Teaching Building Software for Real Users in Grades 11-12 (Level 2): Oklahoma Standard L2.AP.PD.01 Teaching software development process in grades 11-12 (level 2) does not have to be complicated. Picture a startup choosing Agile sprints because its users' needs are expected to change fast. That kind of thinking is exactly what Oklahoma's grades 11-12 (level…
Teaching Designing at Scale: Generalizable Patterns in Grades 11-12 (Level 2): Oklahoma Standard L2.AP.M.02 Teaching computational problem design in grades 11-12 (level 2) does not have to be complicated. Picture a software architect designing one shared scheduling component instead of separate systems for classes, clubs, and practices. That kind of thinking is exactly what Oklahoma's…
Teaching Constructing Solutions: Procedures, Modules & Objects in Grades 11-12 (Level 2): Oklahoma Standard L2.AP.M.01 Teaching object oriented programming in grades 11-12 (level 2) does not have to be complicated. Picture a software engineer designing a payment-processing module that other engineers can call without knowing its internal implementation. That kind of thinking is exactly what…
