Shriram Krishnamurthi: Curriculum Design as an Engineering Problem: Lessons from the Field

Core Philosophy and Goals

• Problem-Solving Approach: Curriculum design should mimic systems engineering by first defining goals and constraints before selecting methods, rather than starting with specific programming languages (e.g., Java vs. Python).
• Bootstrap's Three Primary Goals:
  • Equity: Addressing representation disparities in computer science by ensuring access for underrepresented groups (e.g., female, racial minorities, and lower-income students).
  • Rigor: Maintaining high academic standards, countering the trend of lowering rigor to achieve universal adoption or simplify content.
  • Scale: Designing solutions applicable to large populations without requiring specialized, scarce resources or individualized attention per student.
• Rejection of Traditional Silos: The "everyone should learn CS" premise is best achieved not by requiring CS classes, but by integrating computing concepts into existing universal requirements like algebra, data science, and physics.

Analysis of Delivery Avenues

• Required CS Courses:
  • Constraint Failure: Scales poorly due to the high cost and scarcity of certified CS teachers, who are often poached by the tech industry.
  • Rigor Risk: Mandatory graduation requirements often force a reduction in difficulty to ensure universal passing, compromising rigor.
• Elective CS Courses:
  • Equity Failure: Enrollment is heavily biased toward white and Asian males, reinforcing existing achievement gaps.
  • Curriculum Blockage: Students struggling with core required courses (like Algebra I) are often filtered out of electives before they can access CS, excluding those who might benefit most.
• After-School Programs:
  • Attendance and Continuity: High volunteer turnover (25–30% retention rates) and student absenteeism due to work or family obligations prevent the cumulative learning required for STEM.
  • Equity Barriers: Excludes students who cannot attend after-school hours due to economic necessities or family caregiving roles.
  • Rigor Issues: Lack of standardized training and teacher compensation leads to inconsistent quality and difficulty in maintaining a rigorous, coherent curriculum.

The Integrated Computing Solution (Bootstrap)

• Integration Strategy: Embeds computer science into Algebra, Data Science, and Physics curricula to leverage existing teacher networks and mandatory class attendance.
  • Algebra: Targets the "gateway" subject where 80%+ of students drop out of math, using programming to teach abstract thinking and function concepts.
  • Data Science: Uses real-world data questions to teach statistics and computational thinking, introducing concepts like "Weapons of Math Destruction."
  • Physics: Applies difference equations and simulation to teach calculus concepts earlier than traditional curricula allow.
• Pedagogical Framework:
  • Design Recipe: Students follow a structured, multi-stage process (contract, purpose statement, examples, code, tests) to scaffold learning and reduce the "blank page" frustration syndrome.
  • Transfer Mechanism: Explicitly bridges the gap between programming and mathematics by using identical structural representations (e.g., mapping type specifications to domain/range, test cases to input/output tables).
  • Language Selection: Uses functional programming (Racket) to avoid syntactic distractions (like imperative side effects or floating-point errors) that hinder the transfer of mathematical concepts to code.
  • Assessment: Students create working video games and data reports, culminating in "launch parties" that include professional-style code reviews and math explanations.

Implementation Challenges and Future Directions

• Teacher-Centric Support: Success relies on providing professional development, workbooks, and administrative support to non-CS teachers (math, social studies) rather than focusing on developer tools.
• Structural Barriers: Schools often resist integration due to fear of negatively impacting high-stakes standardized testing scores, even when evidence suggests learning gains.
• Scalability of Research: Longitudinal studies are difficult to conduct due to strict student privacy laws and school district data policies, limiting the ability to track long-term student outcomes.
• Bootstrap Junior: A new curriculum being developed specifically for middle schools to address earlier skill gaps before algebra.
  • Accessibility: Features a block-based environment co-designed with blind programmers to ensure screen reader compatibility (ARIA compliant).
  • Pirate Language: A syntax variant of Racket designed to eliminate parentheses, addressing common complaints from non-CS teachers.
• Pre-Service Training: The organization is actively working to integrate Bootstrap materials into Master of Arts in Teaching (MAT) programs and pre-service teacher curricula to ensure future educators are prepared.
• Interdisciplinary Faculty: The organization advocates for schools to send cohorts of teachers from different disciplines to training, creating a support network that prevents isolation and fosters cross-curricular innovation.

Organizational Status and Resources

• Resource Constraints: The Bootstrap organization operates with a minimal team (approx. four people), many of whom hold full-time professorships, limiting administrative capacity.
• Funding Needs: A primary bottleneck is the lack of dedicated staff to manage relationships with state departments of education and navigate bureaucratic procurement.
• Community Engagement: The organization seeks volunteer contributions for technical development (e.g., JavaScript hacking for accessibility) and advocacy to expand reach.