Back to blog

Notes on Learning Programming

Sep 2020 · 3 mintechlearning
A laptop screen showing lines of code
Photo by David Schultz on Unsplash

I read Learning programming — easy to start, hard to master by Kacper Zagrodzki. It’s about the obstacles people commonly face when learning to code, and it also corrects a few common misconceptions. These are the points I think are worth remembering.

The start really is hard. Unfamiliar terms, new concepts, errors that keep coming — it’s normal to feel overwhelmed. Everyone goes through this phase; what sets people apart is simply how long they stick with it. To keep going, motivation needs maintenance: remember why you started, and break big goals into smaller pieces so progress becomes visible. Taking breaks and rewarding yourself after finishing something also helps.

New technologies keep appearing, and it’s easy to get tempted to try them all at once. It’s better to go deep on one thing than to skim the surface of many. Direction can change over time — what matters is not getting lost among too many choices.

As for math, the belief that you have to be good at math to code isn’t entirely true. In certain fields like data analysis or machine learning it does help, but for most programming work, understanding concepts and the language itself matters far more.

One thing that’s often misunderstood: code review is for learning, not for being judged. Feedback on code is the fastest way to see how someone else looks at the same problem. There’s a line that has stuck in my head — we are not our code. A comment on the code is not a comment on us.

Experience can also be gained before your first job. Personal projects, hackathons, open source contributions, joining communities — all of these produce real experience without having to wait until you’re hired first.

The most honest point comes at the end: this process can’t be rushed. Claims like “become a programmer in a month” are generally unrealistic. What actually works is setting clear goals, practicing consistently, and working on real problems — not just following tutorials.