Computer Science Principles
Course Progress
0/0
Learning Goals 3
→Environment Check: OS tools, Python, Jupyter
→Automation: VS Code, Code Runners
→Portfolio: GitHub, GitHub Pages
3 assignments due
Learning Goals 3
→Data Types: Strings, Numbers, Booleans
→Control Structures: Selection, Iteration
→Modularization: Functions, Classes
Learning Goals 3
→Architecture Design: Frontend-to-Backend
→CI/CD: Git commit, Test, Deploy pipelines
→Project Management: Kanban, Backlog, Burndown
1 assignment due
Learning Goals 3
→Create Performance Task (CPT)
→Frontend Connection
→Backend API endpoints
Learning Goals 3
→Integration: Test & Debug
→Review: Backlog & Grooming
→Retrospective: Improvement
1 assignment due
Learning Goals 3
→AP CSP: Big Ideas and Essential Concepts
→Frontend: User Interface Design
→Backend: APIs and Databases
Learning Goals 3
→HTML, JavaScript, and the DOM
→User Input and DOM Manipulation
→APIs and Asynchronous Fetch
1 assignment due
Learning Goals 3
→Data Serialization: JSON and Python Dictionaries
→API Design: Defining Endpoints and Data Contracts
→Data Modeling: SQLAlchemy and Relational Databases
Learning Goals 4
→Algorithms and Efficiency
→Randomization and Simulation
→CPT Technical Review
→Reflection and Improvement
Learning Goals 3
→Forms: Input Handling and Validation
→Client-Side State: localStorage and User Preferences
→APIs: Fetching and Working with Application Data
Learning Goals 3
→Integration: Combining Team Contributions
→User Experience: UX Refinement
→Testing: End-to-End Application Testing
Learning Goals 3
→Code Review and Debugging
→Documentation: README, Setup, and Usage
→N@tM Presentation Practice
Learning Goals 3
→Flask: Routes, Requests, and Responses
→Authentication: Login, Sessions, and Cookies
→Data Access and Security
Learning Goals 3
→API Development: RESTful Endpoints with Flask
→Development Tools: Postman, Debugging, and Error Handling
→CPT Ideation: Designing a Full Stack Project
Learning Goals 3
→Database Models: SQLite and SQLAlchemy
→Data Operations: CRUD and API Endpoints
→Data Modeling: Designing Persistent Application Data
Learning Goals 4
→CORS: Connecting Frontend and Backend
→REST API Design Principles
→Frontend-Backend Integration
→Full Stack Localhost Pipeline
Learning Goals 3
→AWS EC2 Setup and Configuration
→Database Backup and Restore
→Full Stack Testing and Debugging
Learning Goals 3
→Algorithms and Data Processing
→Machine Learning Concepts
→AI Applications and Limitations
1 assignment due
Learning Goals 3
→Data Collection and Preparation
→Data Structures and Data Modeling
→Data Analysis and Visualization
Learning Goals 3
→AI APIs and Model Integration
→Backend Services and Data Pipelines
→Prototype Development
Learning Goals 3
→Solution Demonstration
→Client Feedback
→Project Planning for Non-Profit Development
Learning Goals 3
→Frontend and Backend Integration
→Database and Data Management
→Feature Development
Home Page Game Feedback
1 min read
•
Assignment
Week 0: Code Runner Review — Home Page Game Feedback
When you first open the Open Coding Society site, you’re redirected straight into a game: CS Pathway — an interactive way to explore the whole course, at /cs-pathway. Before you write any code this trimester, play it and tell us what you found.
Play CS Pathway
- Visit the site’s home page (it redirects you automatically) or go directly to
/cs-pathway. - Play through as far as you can — try to unlock at least one course zone.
Draft Feedback
Take notes as you play, organized into:
- Bugs — anything broken, confusing, or that didn’t behave the way you expected.
- UX Friction — places you got stuck, lost, or weren’t sure what to click or do next.
- Feature Ideas — one thing you’d add or change to make it better.
Open a GitHub Issue
- Create a GitHub Issue in your own repository documenting your feedback — one bullet per bug, friction point, and idea from above.
- Give it a clear, specific title (e.g. “CS Pathway Feedback — Unlock Threshold Unclear on CSP Zone”).
Submit
- Submit the URL to your GitHub Issue as this assignment’s deliverable.
Submit Assignment
Need to update a submission later? Open the submissions dashboard.
Course Timeline
Week 0 Chat click to open
No messages yet.
Week 1 Chat click to open
No messages yet.
Week 2 Chat click to open
No messages yet.
Week 3 Chat click to open
No messages yet.
Week 4 Chat click to open
No messages yet.
Week 5 Chat click to open
No messages yet.
Week 6 Chat click to open
No messages yet.
Week 7 Chat click to open
No messages yet.
Week 8 Chat click to open
No messages yet.
Week 9 Chat click to open
No messages yet.
Week 10 Chat click to open
No messages yet.
Week 11 Chat click to open
No messages yet.
Week 13 Chat click to open
No messages yet.
Week 14 Chat click to open
No messages yet.
Week 15 Chat click to open
No messages yet.
Week 16 Chat click to open
No messages yet.
Week 17 Chat click to open
No messages yet.
Week 25 Chat click to open
No messages yet.
Week 26 Chat click to open
No messages yet.
Week 27 Chat click to open
No messages yet.
Week 28 Chat click to open
No messages yet.
Week 30 Chat click to open
No messages yet.
Week 34 Chat click to open
No messages yet.