Skip to main content

Mathematics and digital technologies · Melbourne

Teaching

Model it clearly, then hand over the thinking. I teach mathematics and digital technologies in Melbourne. This page is about how I teach, what my placement taught me, and what keeps me in the classroom.

Approach

I came to teaching from computer science and systems work, and that shapes what I want from students. Following steps is not enough. I want them to explain why a method works, why a table or a key or a test is there, and to defend that choice to someone else.

So a new idea starts with a worked example, out loud, with the reasoning said plainly. Then students meet something that pushes back: a question that breaks the pattern, a messy dataset, a query that returns 800 rows instead of 7. I keep asking why, and the errors I see become the next lesson's warm-up.

Decisions, not diagrams: three ways to teach database design

This short video is for other digital technologies teachers.

Transcript and resources in the portfolio 

Try it · from Meaning before procedure

“A car drives at 20 metres per second for 5 seconds, how far does it go?”

0123451020time (s)velocity (m/s)20 × 2.5

Distance = speed × time = 20 × 2.5 = 50 m

Read the essay 

How a lesson runs

  1. Retrieve

    Two to four warm-up questions. One is always built from a misconception I saw last lesson.

  2. Frame

    A learning intention and success criteria, where they genuinely help.

  3. Meaning first

    Why the idea works, before the procedure that uses it.

  4. Model

    Worked examples out loud using R.A.P.S.: read, annotate, find the pattern, solve. Then I do, we do, you do.

  5. Practise by demand

    Core, application and challenge questions, so every student is stretched.

  6. Check

    One exit question that tells me who has it.

  7. Consolidate and reflect

    A short summary, selected practice and a few videos. The errors I saw become the next retrieval.

Placement

A term in a senior mathematics classroom.

From May to October 2026 I taught and observed Year 10 Core Mathematics, Mathematical Methods Units 1 and 2 and Specialist Mathematics Units 1 and 2 on placement in Melbourne. Early on I found that knowing how to solve a question did not mean I could explain it clearly, manage the room and tell whether everyone understood. The gap between those things is where I did most of my learning.

The sharpest lessons were small. A poorly chosen example can confuse a class and burn ten minutes without helping anyone, so I learned to pick fewer examples that reveal the reasoning and vary the thinking rather than repeat it. Saying that logarithms "cancel out" hides what is really happening, so I learned to use correct terminology and justify each step. Working through every example loses the students who already have the method, so I learned to release the class to independent work sooner.

I also learned to check understanding every few minutes instead of at the end, with a random name wheel so participation is normal rather than voluntary, and to watch faces for confusion or boredom. Faculty meetings showed me the side of teaching students never see: balancing accessible, medium and hard questions on a test, allowing enough working time per mark, and the care that goes into reviewing a paper before it reaches a class.

Teaching

Secondary teaching placement, Melbourne

Year 10 Core Mathematics, Mathematical Methods Units 1 and 2, Specialist Mathematics Units 1 and 2 · May to October 2026

Study

Master of Teaching (Secondary), Monash University

Mathematics and Digital Technologies

Industry

Systems testing and automation, NEXTDC

Previously DevOps on Monash University's exam platform

Background

BSc, Computational Science and Mathematics, Monash University

Monash Minds alumnus and coach

What I enjoy

The moment a student explains something back to me in their own words, and it is right. That is the whole point of modelling once and then handing over, and it never gets old.

Building materials for a specific class, then watching which parts land. A lesson is a design problem, and I like that the feedback arrives within the hour.

The relationships. On my last day, students told me they appreciated my teaching and asked me to come back. Those conversations carried me through the late nights of preparation and the lessons that did not go to plan, and they are the reason I want to do this.

What I want to carry into my next classroom: purposeful examples, precise explanations, frequent checks for understanding, a better balance between my explanation and their practice, and preparation that is sustainable. The farewell feedback gave me confidence. The detailed feedback from my mentors gave me direction.

My classroom resources and the thinking behind them.

Have something in mind?

Let’s make it click.