Read the error before the fix

We teach how code behaves before we hand over a fix. A traced loop, a stack trace read line by line and an error explained in plain words turn a tutor's hint into something you can reuse on the next problem.

Teaching principles

Plain words first
We name the variable, the loop and the error in ordinary language before any notation. If a term cannot be explained simply, we slow down.
One idea per lesson
Each session carries a single debugging habit or data structure idea. You leave with one thing to practise alone.
Diagrams over jargon
We sketch memory, call stacks and data flow on screen. A drawing of the call stack often explains recursion better than a paragraph.
Honest about limits
A session can explain a concept or review your code; it cannot sit your exam or promise a grade. We say so before you book.

What we do not do

No writing your assignment for you
No answers without a walkthrough
No guaranteed marks or grades
We never ask for your university login

Instructors

The engineers behind the sessions

Maya Ellison
Python and Java
Maya likes to start with the smallest failing example and let you type the fix. She explains loops and classes without hiding behind jargon.
Tomás Ferreira
Data structures
Tomás draws trees and hash tables before touching the keyboard. He asks you to predict what the code will do, then runs it to check.
Priya Nair
Debugging practice
Priya treats a bug as a story with clues, not a failure. She walks through stack traces and test cases until you can spot the next one yourself.

Read the error before the fix

Teaching principles

Plain words first

One idea per lesson

Diagrams over jargon

Honest about limits

The engineers behind the sessions

Maya Ellison

Tomás Ferreira

Priya Nair