What I Carry Forward

I came into my first semester thinking I knew what I signed up for. I had attended hundreds of seminars before, built software for a living, worked daily with AI, and assumed that an EdTech course would mostly confirm what I already understood about education, tools, and systems. But each session, discussion, and workshop challenged my abstract ideas of the Filipino classroom. Listening to my classmates, mostly practicing teachers, showed me the reality and struggles of day-to-day teaching.

Far more than the EdTech concepts and tool discussions, however, are the valuable lessons of what it means to be a wise teacher and EdTech practitioner. Here are some of them, distilled for your benefit.

Pedagogy first, technology second

I came into this Master’s program as a data scientist and software engineer. But this course taught me that I should not be allured by technology. As a builder, before I ask what to build, this course taught me to first examine, “Who is this for, and what do they actually need?”

That shift sounds almost embarrassingly obvious when written down, even for a software engineer like me. But seeing it through the lens of education, I understood: knowing the learner is the diagnosis; the theories and tools are the treatment.

Because of this course, I have come to appreciate learning frameworks more deeply. A framework is what protects a lesson from my own blind spots. TPACK guards against my temptation to over-reach for sophisticated tools. ADDIE forces me to analyze before I design and to evaluate after I implement. SAMR keeps me honest about whether I am actually transforming a task or just digitizing it.

None of these constrain creativity; they prevent self-deception.

Technology amplifies whatever you point it at

This is the single sentence I want to carry into every classroom and every product I build. Aimed at curiosity, technology accelerates learning. Aimed at convenience, it accelerates dependence. Aimed at a poorly planned lesson, it produces a poorly planned lesson with a new distraction.

Therefore, technology alone does not decide if a learning experience is good. The thinking behind it matters more. That puts the responsibility back where it belongs: on the educator, the designer, the human.

The right kinds of friction must be protected

As an engineer, my instinct is removing friction. But education has friction that should not be removed: the discomfort of a hard problem, the slow work of revising a bad draft, the patience to verify before believing. AI in particular can quietly substitute for the cognitive struggle that produces learning itself. Effortless learning, I have come to believe, is often just forgetting in disguise. Part of being a thoughtful EdTech practitioner is knowing which friction to absorb and which to defend.

Equity is not optional

I cannot design for an idealized Filipino learner with stable internet, a personal device, and a quiet study space at home. Carelessly forcing changes without empathy can widen the very gaps I want to close. The same caution applies to AI, to blended learning, to assessment platforms.

EdTech that only works for the connected and well-resourced is inappropriate in the Philippine context. Equity has to be a design constraint from the first sketch, not a disclaimer at the end.

The teacher, not the tool, makes the decision

Across every topic—integration, frameworks, blended learning, assessment, AI—the same conclusion kept surfacing. A school can have the newest tablets and remain stuck at Substitution. A teacher can run a flawless Kahoot! and change no instructional decision. An AI tool can draft a hundred lesson plans and still produce nothing meaningful if no human exercises judgment over them.

We do not have a hardware problem in Philippine education. We have a problem of teacher development, leadership, and pedagogy. Misdiagnosing this as an equipment problem is how budgets get spent and nothing changes.

Human at the center, always

Every framework, case study, and policy we studied pointed to the same conviction: technology should accelerate learning, not impose on learning. That decision belongs to teachers, learners, and the communities they serve.

As someone who builds AI systems, I needed to hear this clearly and often. The instinct of my field is to automate; the discipline this course taught me is to ask first whether something should be automated, and what is lost when it is.

Gratitude

As this semester comes to an end, I want to express my thanks to everyone who made it meaningful. Studying at the University of the Philippines has been an answered prayer for me, and I acknowledge everyone who became a part of this dream come true.

I am deeply thankful to my professor, Teacher Sam Bazer, for his guidance and generosity throughout this semester. I am also grateful for my classmates. Most of them are professional teachers, passionate about becoming even better at their craft and calling. Learning alongside them—and from them—has been one of the most unexpected gifts of this course.

A personal commitment

I entered this program to bridge my technical background with education. What I did not expect was how much the bridge would change me, not just my work. I am leaving the semester more inquisitive about tools, more patient with process, and more convinced that the irreplaceable parts of teaching—provoking curiosity, modeling judgment, noticing a confused student, asking a better question—are exactly the parts I should protect, not “optimize.”

The frameworks gave me language. The case studies gave me examples. But what I am really carrying forward is a question I now ask myself before designing anything: Who is this for, and what will it actually give back to them?

As I face the years ahead in this Master’s program, this class has given me the strong foundation I need to be a better EdTech innovator and practitioner. I now carry much hope and drive for the discoveries and breakthroughs ahead.