Week 8: Personal Retrospective

Today is graduation so, I will keep this short and sweet.

What was the build that you are most proud of and why?

The project I’m most proud of is my electronic dice machine. It pushed me far beyond simply following instructions—I had to troubleshoot wiring errors, revise code multiple times, and really understand how each component worked together. Seeing it function felt like the moment when everything I’d been learning finally clicked.

Looking back at Week 1 through now, how did you grow?

Revisiting my early submissions showed me just how far I’ve come. In the beginning, basic circuits felt overwhelming. I struggled with reading wiring diagrams, identifying errors, and even understanding why an LED wouldn’t turn on. Week by week, I noticed my tone shift from hesitant to confident. By the end of the course, I wasn’t just hoping something would work—I was testing, revising, and explaining why it worked. Each project became a stepping stone in my growth as a maker.

What did you learn that you didn’t know before?

Before this class, microcontrollers, sensors, resistors, and LED displays were terms I’d heard but couldn’t apply. Now I understand not only what they are, but how they interact to form a working system. Through hands-on building—like my breadboard prototypes and electronic dice—I learned how hardware and code depend on each other. Tutorials and examples were helpful, but the real learning happened when I made decisions, fixed mistakes, and figured things out on my own.

How did you actually come to learn this new knowledge?

I learned by doing—and by failing forward. Every broken circuit, error message, or unexpected result forced me to slow down and problem-solve. Over time, I realized I’m far more capable and persistent than I initially believed. My weekly reflections almost read like a story of someone gradually discovering their own skills. By the end, I could evaluate solutions, identify problems quickly, and approach challenges with confidence.

What did you learn about yourself?

At first, my biggest struggles were small technical issues—misplaced wires, missing semicolons, incorrect pin assignments. But as I improved, my challenges evolved. I began asking deeper questions: How can I refine this design? How do I make this more intuitive? How can I enhance accuracy or visual appeal? This shift shows real personal growth—from just getting something to work to understanding how to improve it thoughtfully and intentionally.

What were you telling yourself each week, and what challenges did you notice?

If one of my students turned in the reflections I wrote early on, I would see someone doubting their own abilities. I repeatedly labeled tasks as “hard,” questioned my skills, and hoped things would work. But my builds always showed determination. As the course continued, my challenges shifted from basic troubleshooting to more complex design thinking—proof that my mindset and skillset were evolving at the same time.

Did your challenges change over the course?

Absolutely. What once felt impossible—like wiring stable circuits or debugging code—eventually became routine. By the end, my challenges centered around creativity, usability, and polish. This change reflects a deeper level of understanding and confidence. Instead of trying to survive each assignment, I started thinking about how to elevate my work.

What are your next steps?

Moving forward, I want to push myself with more advanced microcontroller projects and eventually turn prototypes into purposeful products. I’m especially interested in designing interactive builds that combine coding, sensors, and user experience. In my professional life, I plan to integrate more making into my classroom now—and even more so when I become a librarian. I’ve already scheduled time with my librarian to do coding activities with students next week. Long-term, I want to create a Makerspace that supports both students and teachers, sparks curiosity, and brings STEM and creativity together.