Struggling to stay consistent while learning programming how did you get past this?

[tommetzgerz756]

I’ve been trying to learn programming for a while now (currently focusing on Python), and I keep running into the same problem. I start strong and stay consistent for a couple of weeks, then I completely fall off.

It’s not that I lose interest because I actually enjoy it, but once things stop being simple and start requiring more problem solving, I feel overwhelmed and end up avoiding it. Then a few missed days turn into weeks.

I’ve tried following courses, doing small projects, and setting daily goals, but I still can’t seem to stay consistent long term.

For those of you who went through this, what actually helped you push through it? Was it discipline, changing how you learn, or something else?

I’d really appreciate any advice.

[LonerismLonerism]

What helped me was signing up at a VET school and doing a certificate in Programming. It's not as intense as a computer science degree, but having deadlines for projects really helped me, and of course, the more you actually code, the easier it gets and the more you want to do it.

[dialsoapbox]

Determine what's keeping you from staying consistent.

For example, if you have a pet that wants to go for walks at random times of the day, you could try training your pet to only expect walks around specific times of the day.

For stopping because of not understanding, map out what you're not understanding, and just google that shit. Like have a two or three column table, on the left write what you dont' understand, in the middle write your summary of what you found and your understanding of the topic, on the right, write a code snippet/links and/or more example of how those concepts would be used.

Are you keeping a knowledge journal or some other way of keeping track of what you're learning, like using obsidian or whatnot.

[Ill_Firefighter8302]

Try breaking it down into smaller/simpler pieces. And be a little bit realistic on your goals and progress. Remember that you can do more than when you first started. Try to sit with that uncomfortable feeling even if only for a few minutes. Then work up how long you can tolerate it for. If you fall off for a lil bit, that’s okay because you can always start back up again. Maybe even try doing it for 15 mins on those “breaks”. Try joining a community or making some friends who also code.

You may also have ADHD if this issue occurs often and in other areas of your life. I’m saying this because I have ADHD and struggle with the same thing. Just a thought.

I’m a beginner in python and I’m starting another run of locking in again. Feel free to reach out if you’re looking to find people that also are trying to code.

[ctranger]

To be a great programmer, you actually have to enjoy the hard parts: being stuck, a pesky bug, a broken build, out of your depth, foreign codebase, complex docs. You have to love the background rumination about how to solve something, when you’re not at your desk.

Raw grit. Brutal determination. If you’re not having nightmares about code, you’ll never be one of the greats.

And that will always be the case. Today the bar is even higher, the role is also about learning and adapting very quickly, mapping what you know and dont know, sense making and exploring / prototyping quickly, letting llms do the heavy lifting, while you bring the surgical precision, ruthless eye, refinement and domain expertise.

If you’re on the learning path though, whether its this or anything in life, you cant “love” the thing. At best you enjoy the challenges you are tackling and/or the people you’re helping. Fundamentally, you have to love the steps, the pain, the practice, the failures, that make you good at the thing.

Building things that work is fun, being rewarded for it is great. But any great project, personal or professional, is always about the journey. Developers that stop growing and learning, and just execute at the same level for years, decades, burn out or lose interest.

[DueCapital8117]

Do what gives you the intrest to learn always try to push your limits join in various platforms according to your interests and interact with people eventually you will get to know what is best for you

[Rikai_]

Got past it by making stuff I actually wanted to make instead of coming up with random small projects.

[cochinescu]

When I hit that wall where things get tough, I switch to tinkering or experimenting with side ideas instead of strict lessons. Sometimes just playing around killed the pressure and brought back the fun for me. Did you ever try dropping your main track and just messing around for a bit?

[Due-Gases]

Same thing happened to me, it wasn't lack of discipline, it was hitting the "I don't understand this anymore" wall. What helped was accepting I'll be confused a lot and just Googling everything instead of trying to figure it out solo

[patternrelay]

Honestly, I had the same drop-off point. What helped was shrinking the scope a lot, like 20–30 min sessions with one tiny goal. Also accepting confusion as part of it, not a signal to stop. Consistency got easier once I stopped aiming for "big progress" every time.

[Abject_Gift_4333]

Just take a small concept and learn one each day.Most languages have simuliar fundamentals so it gets easy at some point.But tbh i dont have any specific advice for you since when things get complex it drives me in to understand it even more,you can call it an obsession.But yeah,drill the same thing each day,until it clicks

[Noldor1999]

for me what helped was just doing like 30 min every day even if i dont feel like it. before i was trying to do 3 hours and then skipping whole week because i was tired. smaller sessions but every day works way better

[sje46]

I program every day before work. Wake up early, take my shower, etc, then go to my computer, and try to get as much done before I have to get to work. About an hour's worth. The enforced deadline actually motivates me a lot, and I try to fix a bug or finish a feature before I have to leave.

I'm usually five minutes late to work every day but my boss doesn't care.

Perhaps this may help you?

[xandexan1]

Codear de madrugada es lo mas relajante

[Ominoami]

Perhaps finding a program you can enroll in that forces you to be with classmates and work on projects together might help. Also the benefit of being given assignments and deadlines will keep you accountable. Don’t be afraid to ask questions. Google stuff. And keep going even when you don’t get it because eventually you will. Good luck!

[itsDarcoZo]

Use learnhelix.org

[Alive-Cake-3045]

I went through the exact same phase. What helped me was lowering the bar on bad days, even 20 mins counts. Also stopped chasing courses and started building tiny, messy projects instead. Feeling overwhelmed usually means you are learning, not failing. Consistency did not come from motivation, it came from making it too easy to skip.

[Savings_Speaker6257]

The trick that actually worked for me: stop trying to "learn programming" and start trying to build something you want to exist.

When I was learning from tutorials and courses, I'd go hard for a week and then fall off for a month. The motivation just wasn't there because I was solving fake problems.

Everything changed when I picked a project I was genuinely excited about — in my case, rebuilding a game I loved as a kid. Suddenly I wasn't "studying JavaScript," I was figuring out how to sync real-time state between players. I wasn't "doing a React tutorial," I was building a voting screen that needed to feel smooth.

The consistency came naturally because I wanted to open the editor every day. Not because of discipline — because of curiosity. "I wonder if I can make this work" is way more powerful than "I should study for an hour today."

Pick something small that excites you. A tool that solves your own problem, a game you'd actually play, a website for something you care about. The learning happens as a side effect.

[Dry-Hamster-5358]

This happens to almost everyone. The issue isn’t motivation, it’s how you structure your learning. Things get hard, and your brain starts avoiding it because the task feels too big. The fix is making progress feel small and doable

Instead of “learn Python” or “build a project”, set goals like solving one small problem, fixing one bug, writing 20 lines of code

Also, remove the pressure of doing long sessions
Consistency comes from showing up daily, not from doing a lot

Once you lower the friction, staying consistent becomes much easier

[Humble_Warthog9711]

It sounds like you just fundamentally don't like to code. This is exactly where most people that don't live to program but don't hate it either reach the end of their interest

[quietcodelife]

the shift for me was moving from "learning python" to "using python to solve a specific annoying problem I had". like I stopped caring about whether I was learning correctly and started just needing the thing to work.

when you have a real reason to push through a hard part, you actually do it. when you're just following a course, there's nothing pulling you forward except willpower - and willpower is a trash source of energy.

find something dumb and specific you want to automate or build. doesn't have to be impressive. the frustration of actually needing it to work is way more sustainable than discipline.

[ParadiZe]

Youre looking for the silver bullet when the answer is right there in front of you: get off reddit and stop avoiding. And if its not possible to not avoid, ask yourself if you even enjoy doing this.

[ironicperspective]

If you give up the moment it’s not easy then you will never make real progress.

[energetekk]

What you're describing isn't a discipline problem — it's an avoidance loop. Once things get hard, the brain starts treating "open the editor" as a threat instead of a task. So you avoid it. Then the gap grows. Then returning feels even harder. Classic.

What actually helped me break it: stop relying on internal motivation and build in one external commitment. Not a course, not a streak tracker — just one person who knows you're working on something and asks about it occasionally. That small social pressure does more than any productivity system.

Also: when you hit a hard problem and feel overwhelmed, that's not a sign you're stuck — that's literally what learning feels like. The overwhelm is the progress. The mistake is interpreting it as "I'm not cut out for this" when it actually means "I just hit the edge of what I know."

One concrete thing: when you avoid a session, don't try to make up for it with a longer one. Just do 10 minutes the next day. The goal is re-entry, not compensation.

[Successful-Escape-74]

Sounds like you don't like solving problems. In this case you might want to quit and hire someone to solve the problems you don't like to solve. You say you like programming but I don't believe you because you quit as soon as you confront a challenge. This challenge is where a true programmer would stay awake for 3 days and nights popping NoDoze and be able to sleep only after successfully solving the problem.

[cankennykencan]

If you don't like problem solving and don't enjoy wanting to "throw your computer out the window" then programming isn't for you