What I Learned from the Girls in CS Panel

A reflection on insights from college students Michael Hayes, Tanisha Patel, Aadit Mathur, and Neha on navigating CS, building skills, and finding your path.

Panel Image

Girls in CS Panel

Key Takeaways

1. There’s No Single Path Into CS

The panelists came from different backgrounds—some switched majors, others started late, and many discovered CS through unexpected hobbies like Legos, photography, or design. What mattered most was reflection and self-awareness about what drives you, not having it all figured out early.

2. High School Classes & ECs Build Real Skills

AP classes, CS courses, and clubs aren’t just resume builders. They develop time management, communication, and problem-solving skills that transfer directly to college and beyond.

3. Break Big Problems Into Small Steps

Everyone emphasized iteration, timelines, scrum/kanban boards, and focusing on one small piece at a time. This skill—breaking complex problems into manageable chunks—is essential in real-world CS.

4. Project Ideas Come From Real Life

Notice problems around you. Do user interviews, build a small MVP, and improve based on feedback. The best ideas solve actual problems people face.

5. Communication Is As Important As Coding

Being able to explain your code, write clear comments, document your work, and focus on user impact matters just as much as the technical implementation. This is crucial in team environments.

6. College Essays Don’t Need to Be Super Technical

Many panelists focused on impact, curiosity, resilience, or community rather than just CS skills. Admissions officers want to understand who you are, not just what you can code.

7. Project-Based Learning (PBL) Is Extremely Valuable

It teaches initiative, collaboration, and how real-world software is actually built. Mr. Mortenson’s classes exemplify this approach.

8. Take Advantage of Opportunities Early

Network, talk to people in industry, try new things, and don’t be afraid to put yourself out there. These connections and experiences compound over time.

Panel Insights: Q&A Summary

What Inspired Your Major Choice?

  • Neha wanted pre-law until reflection showed CS was a better fit
  • Aadit built Legos as a kid and stayed interested in tech through high school
  • Michael loved the creative satisfaction of filmmaking and found the same in CS
  • Tanisha was drawn to the environment and curriculum at Del Norte

What ECs & Activities Helped?

  • Neha: AP classes for critical thinking, writing, and communication
  • Aadit: CyberPatriot for computer comfort; rigorous coursework built time management
  • Michael: Del Norte’s communication emphasis and an internship at SDSU startup incubator taught him to translate tech for non-technical audiences
  • Tanisha: CSSE, CSP, and CSA programs provided comprehensive foundations

How Do You Break Problems Into Small Steps?

All panelists use agile methodologies: iteration, timelines, kanban boards, scrum boards, and APIs. Michael highlighted designing APIs before writing code, while Tanisha broke ML problems into data, schema, and timeline components.

Where Do Project Ideas Come From?

  • Neha: Human-computer interaction and user research—put users first
  • Aadit: Internships assign tasks; observe everyday life for personal ideas
  • Michael: Customer interviews and MVP/prototype testing reveal what users actually need
  • Tanisha: Real-world problems in ML systems

Did You Write About CS in College Essays?

Most focused on impact, community, curiosity, and resilience rather than technical details. Essays highlighted personal growth and initiative, not just coding skills.

Which High School Skills Transferred to College?

  • Time management and collaboration
  • Grit and stress management
  • Public speaking and presentations
  • Initiative and project planning
  • Independent learning (Stack Overflow, ChatGPT, documentation)

On Code Communication & Collaboration

  • Meaningful commit messages and high-quality comments are essential
  • Talking through code verbally helps ensure everyone is on the same page
  • Documentation shared across the team prevents knowledge silos
  • Focus on user impact rather than technical details when explaining projects

Final Advice

Aadit: Try your best in everything and have fun doing it. If you commit, you can achieve it—whether creating a company, landing an internship, or learning something new.

Michael: Look for PBL courses over lecture-based ones. Explore opportunities outside your degree. Try new things.

Tanisha: Take advantage of project-based learning. Build connections at networking events. Talk to industry professionals and put yourself out there.

Mr. Mortenson: Work really hard in class so you still have time to enjoy life outside of class. Have fun with CS.

What This Means For Me

This panel reinforced that CS success isn’t about being a “natural” programmer from day one. It’s about:

  • Curiosity over certainty
  • Iteration over perfection
  • Communication over isolation
  • Real problems over theoretical exercises
  • Balance between work and life