I Understand Python While Learning, But Forget Most of It After a Week. How Did You Make It Stick?

Use it or lose it, as they say. Repetition is key.

Yes it's normal when learning Python. It's normal when learning anything else, too.

Projects will yield the best results overall, but really just do it all. Most important is to not stop.

To make it stick long-term, you just have to keep doing it.

Repetition

Repetition

Repetition

Repetition

The more you write, the more sticks in your head without looking it up.

At first you're looking up loops and functions syntax, later you know that by heart but looks up pandas docs when doing data manipulation, and then finally the syntax and key functions of the libraries you use every day stick.

It'll happen, don't stop yourself looking things up. Just keep working on tutorials and small projects, trusting that the repetition you need to learn stuff will happen naturally.

For a data engineer, you'll want to be familiar with pandas, pydantic, SQLAlchemy, dagster, and airflow and more broadly, the concepts covered by those packages.

It's kinda like hangovers, if ya never stop drinking you don't have to worry about it.

practice, practice, practice, and, etc...

Just look it up as you go like the rest of us

Do a small code project. Like a ticketing script. Something that makes you really understand and put to use what you have learned, also tweak things as you learn, sometimes it will fail or have a bug, and you get to understand why they follow a standard.

Just imagine you're learning French, German or Italian (whichever language you don't know).

Look, you're not forgetting Python. You're just not using it enough to make it stick. That's the whole thing. The fix isn't reviewing notes more. It's building something small with what you already know. You've got SQL and Linux experience, which is genuinely useful here. Write a Python script that reads a CSV and does something with it. Counts rows, filters records, whatever. Something that connects to work you already understand. That context is what makes syntax stay in your brain. ngl, the people who retain this stuff fastest aren't grinding tutorials. They're solving tiny real problems. Even something dumb like automating a file rename task or pulling data from a folder. The moment code does something useful for you personally, it stops being abstract. And honestly, don't stress about writing from memory without docs. Senior engineers google syntax constantly.

I will freely admit that, even as someone who has written Python, C, and C++ every day in my career for the past 10 years, I spent a good portion of my time researching how to do stuff for the first 3-ish years. Eventually it’s gets beaten into your head, but you really need to be working on it frequently.

Who told you you need to memorize everything? The point is knowing the tools available to you and being able to apply them.

Answering in order:

Yes it’s normal when learning or using any language, Google is key

Repetition

Whatever is more comfortable to you

I google things I’m not sure about, also help()

Theory

Use it once to solve an actual problem in your code, remember a vague idea of it in the future that lets you google it easily. Rinse and repeat.

Use it.

I had the same problem, and making small programs with it made it stick.

Work on a project, learn what you need to for that project, finish the project. Work on another project, learn what you need to for that project, finish the project. ...

Lots of things carry over from one project to the next. If you forgot something you need, just relearn it. This is the best way to learn any subject.

Before you know it you're a star.

You repeat it until it’s engraved on your brain

I take notes in a notebook while learning and read it later when I have free time.

that happens usually what I do is I will code before bed and then half rem cycle my brain will sometimes still dream of what I last did . I will think I've forgotten but then if I trust myself I realize I remember more than I thought.

What is your learning process like?

You practise, make small programs that use the skills you learnt.

But also, it's ok to look stuff up. No one programmes 100% from memory

Theory and exercises introduce you to the concepts. Projects help it stick. Nothing wrong with referring to documentation, you will always need to refer to it.

Make sure to understand OOP concepts and not just memorising syntax. Understand data type structures methods etc

Learn concepts on a fundamental level, learn the theory. The exact words are less important. You can memorize words over time, but if you forget the concept, you're done.

And yes, professional developers forget and search up forgotten syntax all the time. I literally have a second monitor dedicated to googling stuff. I remember code from normal use, I don't waste my time memorizing by heart.

It's all about patterns, algorithms, logic and problem solving. After nearly 18 years total I still look up fairly basic syntax, but the job has gotten easier and I've been able to pick up more complicated projects because of understanding how it works and how the pieces fit together.

If I use it a lot, I eventually remember it (after looking it up repeatedly). Consistency during use works better than trying to remember stuff just in case I need it later.

you're never going to remember everything but through repetition, it'll be much easier to pick up certain concepts and syntax than the first time.

Quelque fois des choses prennent des mois, des années et parfois des décennies. Et suivant l'age, la condition physique et mentale, certaine ne pourront jamais venir. Ne voit pas une critique dans ce que je dis, simplement un constat personnel de mes propres limitations.

I followed along with a project, then after it was done I started fresh all on my own. Had to look a lot of stuff up, but it helped.

I use it everyday since almost ten years

Syntax for any programming language you will get with a click. Main thing you have to focus is problem solving aka algorithms.

Understanding something in the moment and being able to write it from memory a week later are very different skills. For data engineering, I’d prioritize files, functions, error handling, list/dict manipulation, working with CSV/JSON, APIs, SQL and Python together, and basic Pandas. Don’t worry about memorizing syntax, looking things up is normal.

Just books, no videos. Then you read and learn with own inner voice, not voice of a stranger, i think thats the key here. And we developers, also cut & paste code, and use own code templates.

I’ve been writing Python for about 10 years now, I still have to lookup syntax for modules, and forget things I should memorized by now. Just keep using it! Some people like books of projects you can work though, like  automate the boring stuff, but you might find the most value from something domain specific to data engineering. 

Saturation

stats grad here who went through almost the exact same loop ~8 months ago — understand everything in the tutorial, blank out a week later. totally normal, especially coming from a domain where you already know SQL/linux and python feels like starting over.

what actually made it stick for me wasn't reviewing notes or redoing exercises. it was one project i couldn't fake my way through — pulled public dataset (nyc taxi trips), built a small analysis pipeline: download → clean in pandas → aggregate in SQL-ish logic → one chart. took maybe 10 days of an hour/day. by day 6 i was still googling .groupby() syntax, but i stopped forgetting because i was reusing the same 5 patterns every session instead of learning pattern #47 once and moving on.

couple things that helped specifically for the "moving toward data" path:

1) reuse beats coverage. pick 3 pandas operations and use them in 10 different ways before learning 30 new ones. sounds slow, works faster.

2) mirror what you already know. you said you know SQL — i literally rewrote sql queries i already understood into pandas first, then refactored. that bridge made python feel less "syntax in wrong order" and more "same logic, different skin."

3) don't memorize, bookmark. i still google datetime parsing every few weeks. the skill is knowing what to look up, not holding it in RAM. same as production SQL honestly.

4) one deliverable per week. even a ugly jupyter notebook with 3 charts and a readme. deliverables force integration; exercises don't.

if you're heading toward data engineering specifically, the project that unlocked it for me was less "learn python" and more "automate one annoying manual step i was already doing" — even something dumb like renaming weekly csv exports. motivation from real friction > motivation from course completion.

The more you use specific concepts, the more you remember them. 

Nothing wrong just look your old code, or Google or ask ai to recall things, it's more important to know some specific thing is possible to do at all.

trauma

Of course it's normal. It's super normal to forget what you've learned. Just review and practice. Regarding question number 3, you should start with the theory, then practice what you've learned on simple things, and only then create more complex projects. I learned with theory and by always practicing to solidify my understanding. The topics are: Creating graphs, manipulating Excel, and data analysis itself with Pandas.

This time, try using it in making projects before learning new topics. Try putting the things that you've learnt in chatgpt and ask for it to give some suggestions and then choose something that interests you the most.

it would feel a bit difficult at first because the foundational things have to be used in a slightly different approach but is completely normal

Yeah man, that's how it is. Learning to code isn't about syntax. I promise you, many really great coders google for common syntax every day. The key is knowing that you need a loop, not how exactly to write one.

Eventually you write enough loops that you just remember. But there will be tons of stuff that you don't use often enough to memorize. And who cares. The important part is knowing that you need a particular piece. You can always google the syntax.

Study the patterns. Don't try to memorize commands.

Yes you learn best practices that’s all you need. Have fun it’s how you discover.

What I can recommend is comment some area so you know what it does. And don’t comment other areas let your code be self commenting.

Honestly, looking at references is something you'll do the rest of your Python career. I still do that, to find things like floor division (// if you were wondering). Don't stress.

you need to build something that applies the concepts you learned to have them stick

Hi, What you’re experiencing is completely normal when learning Python. Forgetting concepts after a few days does not mean you are not learning properly — it usually means the knowledge has not yet been reinforced through enough practice and application. In my experience, Python becomes easier to retain when you shift from “studying” to “building.” Instead of only reading concepts, try applying them immediately in small projects or exercises. Even simple programs help reinforce loops, functions, and data structures much more effectively than passive learning. It is also important to understand that even experienced developers do not remember everything from memory. They frequently refer to documentation and examples. The key skill is not memorization, but knowing how to approach and solve problems. For Data Engineering specifically, I would suggest focusing on: Core Python fundamentals (functions, loops, dictionaries) Working with data formats (CSV, JSON) SQL Basic APIs and data retrieval Pandas (once comfortable with basics) Consistency is more important than intensity. Regular small practice will naturally improve retention over time. You are on the right path — this phase is part of the learning process

I used a notebook where I wrote the more used command. Also I add, time to time, the new one I always use.

This is why I do programming challenges.

AI can generate impressive code and such, but without ME doing the code by myself, over and over and over, I will keep forgetting it. That's why I practice within small coding sessions, doing creative, personal projects, and solving problems, just to let it stick to me.

While learning python , make sure you takes notes Before moving on to the next chapter. Revise the previous one .also practice regularly as you learn so that you don't forget what you have studied

This is 100% normal. Python is a tool, not a memorization test. The problem isn't your memory. The problem is you're learning without applying. Stop watching tutorials. Start building.The most effective way to retain Python:

1. Pick a small project (not a to-do list)

2. Build it from scratch

3. Google everything you don't know

4. Repeat

For Data Engineering specifically:

- Pandas (this is mandatory)

- SQLAlchemy or similar ORM

- Data pipelines (ETL/ELT concepts)

- Working with APIs and JSON

- Basic cloud (AWS/GCP/Azure)

Don't worry about forgetting syntax. Every developer Googles things daily. What matters is knowing WHAT is possible and HOW to find the answer quickly.

Build something real. Start with a simple data pipeline. Pull data from an API, clean it, store it in a database. You'll learn more in 2 hours of building than 2 weeks of watching.

For the keywords

What can I build with just python

Honestly, the thing that made Python stick for me was building small scripts that solved real problems I actually had. Started with a file organizer for my messy downloads folder. Then a renamer that sorts by date. Then a job scraper for Craigslist. Nothing fancy — just tools I'd actually use. The key: don't study syntax in isolation. Learn `os` because you need to move files. Learn `requests` because you want to scrape a website. Learn `datetime` because you want timestamps. The library becomes tied to a real memory, not just a textbook example.

For data engineering specifically, prioritize `pandas`, `sqlite3`, and `requests` those three alone cover 80% of what you'll need. Build a pipeline that pulls data from an API, cleans it, and dumps it into a SQLite database. That one project teaches more than a month of tutorials.

You'll forget syntax. Everyone does. That's what documentation is for. What sticks is knowing *what's possible* and which library to reach for.

You have to write it and repeat it to the point where you can write the entire code in your head

The repetitions and practises are keys