CHAPTER 5

The Intersection of Technology and Education: Embracing Failure and Active Learning

When I first took on the role of a teaching assistant at UC Berkeley, I was filled with a mix of excitement and trepidation. The memory of my own experiences as a student was fresh, particularly the time I had to correct my TA’s mistake on the whiteboard. I could still recall the awkward silence that followed, the way the room seemed to freeze as I pointed out the error, and the visible discomfort on my TA’s face as he realized his mistake. It was a moment that had left me feeling embarrassed, not only for myself but for him as well. Now, as I stood in his shoes, I was determined to avoid making the same misstep. I wanted to be the perfect TA—knowledgeable, precise, and above all, flawless.

But perfection, as I soon learned, is an impossible standard. My first sessions were marked by a constant fear of making a mistake. Each time I approached the whiteboard, I felt a knot in my stomach, my hand hovering just above the marker, the memory of that past embarrassment holding me back. My focus was so fixated on getting everything right that I found myself missing out on the more important aspects of teaching—connecting with the students, engaging with their questions, and fostering a supportive learning environment.

One day, during a particularly challenging lab session, a student approached me with a question that caught me off guard. It was a complex coding problem, one that I hadn’t anticipated. As I began to work through it on the whiteboard, I realized that I didn’t have a clear answer. The familiar panic began to rise, but this time, something inside me shifted. Instead of freezing, I turned to the student and said, “This is a tough one. Let’s figure it out together.”

In that moment, the dynamic of the room changed. The students leaned in, watching as we worked through the problem collaboratively. The pressure to be perfect dissipated, replaced by a sense of shared discovery. We made mistakes along the way, but each one became a stepping stone to deeper understanding. By the time we arrived at the solution, the student wasn’t just satisfied—she was empowered. And so was I.

This experience was a turning point for me. It made me realize that teaching wasn’t about being an infallible source of knowledge; it was about creating an environment where mistakes were part of the learning process, where the focus was on growth rather than perfection. But I also knew that this mindset alone wouldn’t be enough. I needed a way to support my students more effectively, to provide them with the feedback they needed without the constraints of my own fallibility.

That’s when I turned my attention to the autograder system. At the time, the autograder was a powerful but limited tool. It could process student submissions and flag errors, but it lacked the depth needed to truly enhance the learning experience. The feedback it provided was binary—right or wrong—without the context or guidance necessary to turn those mistakes into learning opportunities. I saw the potential for something more, something that could transform the autograder from a simple assessment tool into a catalyst for meaningful, self-reflective learning.

I joined the backend development team with a clear vision: to create a system that not only evaluated student work but also supported them in their educational journey. I wanted to move beyond the traditional, ancient pedagogical model where learning was a one-way transmission of knowledge from teacher to student, often mediated through tools like the whiteboard. Instead, I envisioned a student-centered approach—one that was backed by pedagogical research, inspired by active learning practices, and powered by innovative technology.

The work was challenging but immensely fulfilling. I dove deep into the codebase, collaborating with other developers to implement features that would make the autograder more responsive to the needs of the students. One of the key innovations was the development of a system that could map student errors to conceptual key points. Instead of simply telling a student that their code was incorrect, the autograder would now provide detailed feedback, linking the error to the underlying concept that needed reinforcement.

For instance, if a student was struggling with loops, the autograder would identify not just the location of the error, but also provide insights into why the error occurred and how it related to the broader concept of loops and iterations. This transformed the feedback from a simple “right or wrong” judgment into a teaching moment—one that encouraged students to reflect on their mistakes, understand the underlying principles, and improve their skills in a targeted, meaningful way.

As the autograder evolved, so too did my approach to teaching. I began to see my role not as the gatekeeper of knowledge, but as a facilitator of learning. The technology I had helped develop allowed me to focus more on the human aspects of education—fostering a supportive, collaborative environment where students felt safe to explore, question, and even fail. I encouraged peer pedagogy, where students would learn from one another, sharing insights and strategies. The classroom became a community of learners, each supporting the other in their journey.

The shift from traditional, top-down teaching to a more dynamic, student-centered approach was gradual, but its impact was profound. The students were no longer passive recipients of information; they were active participants in their own education. The autograder provided them with the tools they needed to take ownership of their learning, while the classroom environment empowered them to engage deeply with the material.

One of the most memorable moments came towards the end of the semester. A student who had struggled with the material early on approached me after class. “I just wanted to say thank you,” she said, her voice filled with genuine appreciation. “The feedback from the autograder really helped me understand where I was going wrong. It wasn’t just about getting the right answer—I actually learned how to think differently about the problems.”

Her words were a testament to the transformative power of technology when it is used not just as a tool for efficiency, but as an enabler of deeper, more meaningful learning. The autograder had become more than just a system for grading assignments—it was a bridge between technology and pedagogy, enhancing the learning experience in ways that were both innovative and deeply rooted in educational research.

Through this journey, I came to understand that being a changemaker isn’t about a single, dramatic moment of transformation. It’s a gradual process, a series of small, deliberate steps that lead to a larger shift in perspective and practice. My work on the autograder was just one part of that journey—a step towards creating an educational environment that was not only more effective but also more human.

I learned that mistakes are not the enemy of learning; they are its foundation. By embracing the imperfections inherent in both teaching and technology, we can create a system that supports students in their growth, encourages critical thinking, and fosters a lifelong love of learning. The intersection of technology and education is a place of immense possibility, where innovation can lead to profound change—not just in how we teach, but in how we learn and grow as individuals.

As I continue on this path, I remain committed to the principles that have guided me thus far: the belief in the power of technology as an enabler of education, the importance of a student-centered approach, and the understanding that true change is a process—one that requires patience, persistence, and a willingness to embrace both the challenges and the opportunities that come with it. The autograder project was a testament to these values, and it is my hope that the lessons learned from this experience will continue to inspire and uplift, just as the tool itself has done for the students it serves.