Day 19-Presentation Preparations

View above video on Youtube for English subtitles

See Code at https://github.com/vittorio522/vitto-repository

The current education system's overemphasis on standardized testing hinders practical skill development. Parents and administrators primarily view test scores as the sole measure of learning, creating a gridlock that prevents the integration of practical skills like circuitry or mechanical design into the standard curriculum. There is a widespread fear that dedicating time to these alternative subjects, rather than traditional topics like ancient Greece or Latin, will negatively impact students' test scores. Because of this ongoing opposition and the lack of time during the regular school day, hands-on skill development currently has to be relegated to extracurricular programs. 

To overcome this resistance to educational reform, advocates must gather and share compelling success stories. We need to highlight narratives of students who took alternative educational paths and achieved high levels of success, such as reaching the PhD level at MIT or becoming leaders in their respective fields. Sharing diverse stories that demonstrate how experiential learning enhances rather than degrades education can help prove to hesitant administrators and politicians that this approach is effective. Once teachers implement these methods and witness the positive changes in how kids learn—which can take up to a year to fully recognize—they also become powerful advocates who can share their firsthand experiences. Furthermore, institutional backing, such as formal research data from MIT, is crucial to validate these stories and apply top-down pressure for systemic change. 

Hands-on learning programs should be inclusive environments that appeal to a broad range of students, rather than isolating traditional high achievers. Programs like  FIRST Robotics often suffer from the stereotype that they are silently focused spaces designed solely for "nerds" who only use screwdrivers. Instead, these programs should be fun, social spaces that welcome artists, musicians, and typical students alongside robotics enthusiasts. By bringing together a diverse team rather than segmenting students by perceived intelligence, learning occurs in a much better, more collaborative context. While rigorous, specialized classes—such as the intense curriculum found at exam schools like Boston Latin—have their place and provide valuable structure, they should not constitute a student's entire educational diet. 

The structure of the modern school day creates a fragmented and stressful learning environment that lacks meaningful context. Students are forced to switch between completely unrelated topics every hour, a jarring process comparable to forcing an adult to rotate hourly between sales, production, finance, and legal departments. This rapid switching provides no continuity or flow, stripping the educational material of its meaning and placing enormous stress on the children. The current model functions merely as a "teaching system" where educators deliver information, and students are subsequently punished if they cannot independently figure it out. For example, when a student fails a subject like math, the system simply forces them to endure more of the same ineffective instruction in summer school, rather than addressing the environmental or pedagogical root causes of their struggles. 

Where EDW Could Improve:

• Mentors should come prepared with better tech skills, particularly in the areas of electronics, microntrollers, and coding
  
  
• Students need to be more adept in teaching themselves technical skills- in the workforce, professionals are expected to pick up new skills on their own
  
  
• After the initial ideation, students should research precedents- how have others solved this problem- and document websites and projects examined
  
  
• Presentations should include:
  
  
• Project Title and Team Members
• Project overview- what is the problem they are trying to solve?
• Precedents
• Bill of Materials
• Technical Diagram
• Circuit Diagram
• Code and design files
• Results
• Next Steps