analytics #20
Description
CSA Retrospective: Big Six Framework & Platform Organization
Author: Alex Rubio
Project: Big Six Learning Platform (reQUESTers ecosystem)
Period: November 2025 – January 2026
Overview
This retrospective documents my contributions to the reQUESTers platform, focusing on structure, frontend organization, and long-term scalability. My work centered on designing the Big Six framework, improving content clarity, organizing frontend materials, and planning systems that support features like certificates, quests, and interactive learning tools.
Rather than adding isolated features, I focused on building a strong structural foundation to make the platform easier to understand, maintain, and expand over time.
Key Contributions
- Designed and implemented the Big Six framework
- Condensed and reorganized content for clarity and consistency
- Improved frontend structure and UI organization
- Planned a unified lesson system with interactive components
- Built automation tools to maintain long-term project organization
- Applied AP CSA concepts through FRQ-style problem solving
1. Big Six Framework Development
Problem Statement
As the platform expanded, content became fragmented across multiple lessons, notebooks, and modules. There was no consistent structure explaining how topics connected, which made navigation confusing and limited scalability. This also reduced the effectiveness of future systems like certificates and quests, which rely on consistent learning paths.
Solution: The Big Six Framework
I designed the Big Six framework to group essential computer science concepts into six core areas:
- Frontend
- Backend
- Data Visualization
- Analytics
- Artificial Intelligence
- Resume & Career Development
This framework provides a clear organizational model for users and a scalable foundation for future development.
Contributions
- Designed the Big Six framework from the ground up
- Defined how lessons and submodules map into each category
- Used the framework to guide content flow and navigation
- Ensured consistency so new content could be added without breaking structure
2. Unified Lesson & Interactive Planning
Objective
Combine existing lessons and submodules into one cohesive learning experience rather than scattered, disconnected content.
Plan
Each Big Six category contributes its core ideas into a single main module, supported by interactive tools that reinforce learning through practice.
flowchart TB
A["AI Lesson"] --> B["One Unified Big Six Lesson"]
n1["Frontend Lesson"] --> B
n2["Backend Lesson"] --> B
n3["Data Visualization Lesson"] --> B
n4["Analytics Lesson"] --> B
n5["Resume Lesson"] --> B
B --> C{"Interactives"}
C --> D["AI Prompt Builder"]
C --> E["Postman / API Simulator"]
C --> F["Practice Interviews"]
C --> G["Graphs & Analytics"]
C --> H["Markdown Editor"]
3. File Condensing & Content Clarity
Problem
As content accumulated, files became repetitive, overly long, and difficult to navigate. This created unnecessary complexity for users.
Solution
I condensed and reorganized content to improve clarity while preserving essential information.
Contributions
- Streamlined large and repetitive files
- Removed unnecessary duplication
- Reorganized content to align with the Big Six framework
- Improved readability and reduced user confusion
4. Frontend Organization & UI Improvements
Objective
Improve usability and visual clarity to create a more user-friendly experience.
Contributions
- Standardized formatting across lessons and pages
- Improved navigation consistency
- Used a common layout to reduce cognitive load
- Focused on clean structure rather than overcomplicated visuals
5. Automation: Junk File Archiving System
Problem
Outdated Markdown notebooks accumulated over time, making the project harder to manage manually.
Solution
I designed an automated archiving system that safely moves inactive files instead of deleting them.
Implementation Overview
- Scans the
/notebooksdirectory - Filters for
.mdfiles - Checks last modified dates
- Moves files inactive for 60+ days into
/junk - Preserves important files using front matter metadata
Impact
- Reduced clutter
- Improved long-term maintainability
- Created a reversible, low-risk system
6. AP CSA FRQ 2 Reflection
Struggle
While implementing the AP CSA 2024 FRQ 2 Scoreboard problem, the program initially failed to run because Java requires exactly one public class containing the main method.
Resolution
I analyzed the error, identified Main as the entry point, and declared it as public. The logic itself required no changes.
Takeaway
This reinforced the importance of understanding language-level rules, not just algorithm correctness, especially in exam-style environments.
7. Planning & Burndown Schedule
Big Six Module Burndown
- Week 1: Combine existing modules
- Week 2: Condense content and improve layout
- Week 3: Finalize Big Six main module
- Week 4: Certificate system across all six lessons
- Week 5: Additional interactive features
- Week 6: Deployment and testing
Quests are tracked in hacks/cs-portfolio-quest.
8. Reflection & Learnings
Technical Skills Developed
- Structural system design
- Content organization at scale
- Frontend usability planning
- Automation for maintainability
- AP CSA problem-solving strategies
Soft Skills Developed
- Long-term planning
- Technical communication
- Iterative improvement
- Collaboration across teams and scrums
9. Self-Assessment
Self Grade: 0.87 / 1.0
Justification
My work focused on high-impact structural improvements rather than isolated features. The Big Six framework, unified lesson planning, and content organization created a scalable foundation that supports future systems like certificates and quests.
The slight deduction reflects that some features are still in progress, but the overall direction, planning, and impact of my contributions are strong.