Night at the Museum
Date: May 27
Location: DNHS A101
Extra Credit Theme: What inspired me about a different CS course?
Proof of Experience
Caption:
Visiting CSSE
Before the Event
I expected all the computer science presentations to look relatively the same—just standard code and basic outputs. I assumed every class was building similar types of software, just at different difficulty levels.
Curiosity Before Attending
Since my APCSA class focuses heavily on building robust, fully functional systems, I was highly curious to see what the other tracks were doing. I specifically wanted to see the Game Development projects in CSSE and the rapid prototyping concepts built by the APCSP students.
What I Saw
I spent the full hour and a half exploring. I attended the CSSE game dev project presentations at 6:00 PM, the APCSP prototype presentations at 6:30 PM, and cruised the various elective booths before the 7:00 PM APCSA block.
Most Interesting Thing I Saw
The most interesting thing was seeing the distinct stages of software development laid out across the different classes. APCSP showcased brilliant, early-stage prototypes, while CSSE showed highly interactive, user-focused game development.
What I Learned
I learned how the courses act like a real-world software pipeline. APCSP teaches how to quickly build a working prototype to prove a concept. CSSE focuses on user engagement, game loops, and visual interaction. APCSA takes those foundational ideas and engineers them into robust, fully functional systems that go far beyond a simple prototype.
What Surprised Me
I was surprised by the sheer creativity in the CSSE game dev projects. They had to balance strict coding logic with art, design, and user experience, which is a completely different skillset than just writing backend algorithms.
What Inspired Me
The fast-paced ideation in the APCSP prototypes and the creative engagement in the CSSE games were incredibly inspiring. It showed me that coding isn’t just about making a system work; it’s about making a system that users actually want to interact with.
Personal Connection
I love the heavy technical architecture we build in APCSA, but seeing the CSSE game dev projects inspired me to blend more visual creativity and interactive design into the fully functional systems I build in the future.
Interaction
Person or group I learned from: I spoke to a few of the CSSE game developers and APCSP students during the transition between the 6:00 PM and 6:30 PM blocks.
The APCSP students explained how they used block-based or early-stage coding to rapidly test their ideas as prototypes. The CSSE students showed me how they handled collision detection and game states to make their software fun and responsive.
Depth of Experience
It completely changed my perspective on the software lifecycle. It made me realize that a “prototype” (like in APCSP) is just step one, “game dev” (CSSE) is a specialized branch of engagement, and “fully functional systems” (APCSA) are the ultimate goal for scalable, real-world software.
Connection to CS or Future Goals
It connects directly to my APCSA coursework. Seeing the initial prototype stages in APCSP reminded me why we work so hard in APCSA to ensure our code is fully fleshed out, handles edge cases, and functions as a complete system rather than just a proof-of-concept.
Final Reflection
N@tM was meaningful because it gave me a comprehensive, top-down view of our school’s entire CS pathway. Experiencing the progression from prototypes to games to fully functional architecture demonstrated exactly how different aspects of technology interconnect.
Biggest Takeaway
Seeing the progression of DNHS computer science courses proves that great software starts with a strong prototype (APCSP), thrives on engaging design (CSSE), and relies on the fully functional, rigorous architecture taught in APCSA.