You know this feeling.
You watch the lesson. You read the chapter. You copy the example, and it works.
Then the exercise changes one small thing, and you are stuck.
It was never a memory problem. You were given the answer before you had the question.
Try it the other way
Question first.
What does this print?
x = 4
x += 2
print(x * 2)Not this one. Read it line by line: what is x when it is printed?
12. x becomes 6, then 6 × 2. You have seen this a hundred times.
Now change one small thing.
What does this print?
a = [1, 2]
b = a
b.append(3)
print(a)Almost everyone says that the first time. It prints [1, 2, 3]. b = a did not copy the list. It gave the same list a second name, so changing b changes a.
[1, 2, 3]. b = a did not copy the list. It gave the same list a second name, so changing b changes a.
You will remember that. Not because you memorised it. Because you saw why.
That was fifteen seconds of Understand.
Every lesson works like this. One small idea. Then you predict, you try, you break it, you fix it. You write real code and run it right on the page, with nothing to install.
The feedback comes at once, while you still care about the answer. And you do not move on because a video ended. You move on because you can do it.
Starting with
-
Python
From your first
print()to recursion, files and classes. The place to begin if you have never written a line. -
C++
Types, memory, pointers, classes, and why they behave the way they do. You write it and run it right here in the browser.
-
Full‑Stack Web Development
From Python foundations to a real web application, built with Django and put online by you.
Programming is where we start. It is not where we stop.
Not another library of courses.
A place where things finally make sense.
Understand
Coming soon.
understand.ma