10+ years building software professionally. 50+ students taught. One focus: making sure you actually understand the code, not just submit it.
My job is to make sure they understand it.
I'm a Senior Software Engineer with a Master's degree in Computer Science and over 10+ years of real industry experience ,working with enterprise systems, cloud platforms, and professional engineering teams. I've seen firsthand the difference between someone who can pass a test and someone who can think through a problem under pressure.
I started tutoring because I kept noticing the same gap: students who could produce code but couldn't explain why it worked. That's fine for homework. It's a problem in a closed-book exam.
So I built my teaching practice around closing that gap. Every session is structured around your specific course and goals ,not generic content. I use real debugging scenarios, industry-standard code review, and exam-style questioning.
Computer Science
Senior Software Engineer
Working With Children Check
100+ students taught
Online & in-person (Point Cook, up to 5km)
Three pillars that shape every single session.
I never show code without explaining the real-world problem it solves first. You'll understand why a loop exists before you write one. That understanding is what stays with you in the exam room.
Abstract concepts become concrete through everyday analogies. A class is a blueprint. A pointer is a sticky note with an address. Memory allocation is renting storage space. When the analogy clicks, the code clicks.
If I use a technical term, I explain it plainly first. There are no stupid questions in my sessions ,only concepts waiting for the right explanation.
Not just syntax. The thinking and habits that make a programmer.
Breaking down a problem before touching the keyboard. Pseudocode. Flowcharts. Thinking out loud.
How to read an error message. How to trace through code. How to fix bugs without randomly changing things.
For HSC and university assessments ,how to design the solution, not just write code.
Readable code, meaningful variable names, inline comments ,the habits that make your code credible to employers and markers.