u/Excellent_Pick_8186

When I started learning C, I could follow tutorials and understand what the instructor was doing.

But the first time I closed the tutorial and tried to write a small program completely on my own, I realized I didn't remember nearly as much as I thought I did.

I got stuck on simple things, made stupid mistakes, and had to look up a few things.

But honestly, that was probably the first time I felt like I was actually learning to program instead of just following along with someone else.

Now I'm trying to spend more time solving small problems without immediately looking at the solution.

When I first learned pointers in C, I kept thinking of a pointer as another variable that somehow contained the value of another variable.

The concept finally clicked when I stopped thinking about the value itself and started thinking about the memory address where that value is stored.

Once I understood the relationship between & (address-of) and * (dereferencing), pointers became much less mysterious.

I'm still practicing pointers, but this was one of those concepts where a small change in perspective made everything easier.

When I first started learning C, I thought i++ and ++i were basically interchangeable because both increase the value of i by 1.

Then I saw them being used inside expressions and realized that the difference is actually about when the value is used versus when it is incremented.

That was one of those small C concepts that looked obvious until I actually had to predict the output of a program.

Now whenever I see ++i or i++, I pay attention to what happens to the value before and after the expression is evaluated.

When I started learning C, I mostly thought about code in terms of lines and syntax.

Recently I started paying more attention to what actually happens when the program runs — compilation, memory, variables, stack, etc.

It made me realize that understanding what happens “behind the code” makes programming concepts much easier to connect.

What programming concept made you stop thinking only about syntax and start understanding what was actually happening underneath?