How Do You Stay Consistent While Learning to Code?

I Love Programming
1

I’ve been wondering how other people manage to stay consistent when learning programming.

For me, the difficult part isn’t always understanding a topic. Sometimes it’s maintaining the habit of practicing regularly, especially when work or other responsibilities get in the way.

I’m curious about what works for other developers and learners:

  • Do you set a specific number of hours or coding problems per day?

  • Do you work on projects while learning, or focus mainly on courses?

  • How do you handle days when you don’t feel motivated?

  • Do you follow a fixed learning roadmap, or learn whatever interests you at the time?

  • How do you decide when you’re ready to move on from one technology to another?

I’d especially like to hear from people who started as complete beginners. What helped you stay consistent during the first few months?

Any practical routines or lessons from your own experience would be really helpful.

1 Like
2

Hello! I am still learning HTML, but I know I came a long way from what I was first doing!

Anyway, off of that,
I find that, working on a simpleish project and then expanding it after the core of the project is done helps me a lot!

(Note: This is for an example): I was/am working on a pixel drawing game, and I made the core parts of the drawing in under 2 hours with me searching up how to do certain things, and somehow making it already optimized.
Anyway, I ended up doing that, then over a span of 3 weeks, I added 9-10 different buttons and number values for the different things like layers, step size, etc.

what I am trying to say is that, starting small and expanding actually helps a LOT especially if you learn REALLY quickly.
When you do this, you learn things that are the “basics” of the project, then more complicated things.

I don’t really set a number of hours to work on the projects I am working on, I just do it more as I feel (mostly because I don’t really have a strict time schedule on when it needs to be done. If I did, I probably would have at least 1-2 hours of working on the code. More if I am on a roll.)

I handle days when I don’t feel motivated by just taking a break. If you push yourself too much, you’ll get burnt out. If you’re not motivated, you probably are getting close to burning out, which will make it worse if you keep trying to push yourself too much.

I think I already kind of explained this, but I don’t do a “fixed” learning roadmap, I just go with the flow. Like, if I want to add something to the game I am making, I add it, and I learn while I do it.

From what I interpret, you mean by “technology”, I just move from one thing to another. To be fair though, I do have ADHD, so that is one thing. Also, if you move from one to another, that’s also allowing you to have different challenges to work with rather than having the same/similar ones constantly. It doesn’t really let you learn when you repeat something without variety.

What I would recommend is trying different things! It’s always good to try something, find out it don’t work for you, change it a little. That way you can also find the ways that work, and so you can bounce through a few that work. You can get burnt out with repeating one type schedule, so if you change it up a little, that will allow you to be able to keep your motivation! :3

Now, this is all things that work for me. I don’t know what would work for you, but I do suggest that you try to find things that work for you! It took me a while to find what works for me, and I still kind of am! But that’s okay!

Anyway, that’s all!
Sukaira is gone! (Probably will respond to replies)

1 Like
3

Hi @tauqirashraf

As a beginner, start small. really small. Even one hour spread out over a week.

Learning to code is tough. Most concepts won’t make sense and you have to go on to the next thing, and apply knowledge which hasn’t had time to really settle in.

When things start to get easy or you feel bored, then slowly increase the time. Maybe one hour per day after a few months.

Even though it may sound like slow going, you are giving yourself time to really absorb the material. Within a half year you may not even realise how much progress you’ve made. A lot of the problems people talk about is forgetting stuff they learnt.

Learning is a process which happens when your brain organises knowledge and information while you are sleeping. If you “learnt” something new today, but cannot recall it a few weeks later, you didn’t really learn it in the first place.

Try a flexible schedule and see what works for you at the time. You can always adjust as your needs change.

Learning theory is one thing. Getting hands on and applying that theory helps build essential skills like problem solving, research, and dealing with your emotions.

Listen to what your mind and body are telling you and take breaks. Taking a few days, weeks, or months isn’t really going to hurt in the long run. If you keep going when you are not fully focused you are not making the most of your limited time.

Learning new things is a part of coding. There are new frameworks, methods, tools, languages, the list is quite endless. If something interests you, then follow it. If you start something, spend time deciding whether or not to do it in the first place, then make sure to finish it. A short detour is okay.

When you have learnt 80% of the material, then it’s time to move on. Before you do, build a few projects that can demonstrate your skills and abilities.

Happy coding

1 Like
4

Well, when I was a beginner in coding, I was struggling a lot, like what to code, how to code, etc. Moreover, i had less resources from where I could get information regarding this or to develop my self. So, what i did is, rather relying on other things, I started to develop my skills on my own..Day by day, my experience, skills and thought process grew more matured and developed..
So, i would like to say that try to take as less help as much as you can and try things on your own , because that’s is the ultimate thing that gonna help you to develop your skills, experience and thought process in a systematic manner​:+1:
And, last but not the least, happy coding!

5

What helped me most early on was lowering the daily bar. When work got busy, aiming for an hour or two usually led to skipping days entirely. Committing to just twenty minutes of writing code made it much easier to sit down at the keyboard, and most days I ended up staying longer once the initial friction was gone.

Pairing short tutorials directly with small throwaway experiments also kept things grounded. Reading docs or watching videos without immediately testing the concepts in an editor made it hard for things to stick.

6

What worked best for me when starting out was lowering the bar for what counted as a coding day. Instead of aiming for two uninterrupted hours, I committed to sitting down for 20 or 30 minutes, even if it was just writing a couple of functions or reviewing syntax. Most days that momentum carried me further, and on low-energy days, at least the habit didn’t break. Building small, slightly ugly projects alongside courses also kept things grounded because you run into real errors rather than just following along with clean examples.

7

One thing that helped me think about the “when do I move on” part: define a small build for each topic before you start, like “after this I should be able to make X without looking anything up.” Then you’re done with the topic when you can do that, not when the course ends. It also fixes the consistency problem a bit, because each session has a clear next step instead of “study more.”

Also, after each session, write one line on what you could do from memory at the end of it. If you can’t remember it a few days later, that’s your cue to redo it instead of moving on.

Also one disclosure, I am working as an intern at Marevlo. It is a website that helps you do what I mentioned above and much more. If you are interested to try it out, I would love to hear your experience so we can improve the website. But the approach I shared above works for any resource.

8

I think having a small project makes a big difference. Courses can be useful for learning the basics, but it’s easier to stay motivated when you’re actually building something and have a reason to solve the next problem.

I also wouldn’t worry too much about hitting a fixed number of hours every day. Some days you might have two hours, other days only 20 minutes. Keeping the habit alive seems more important than meeting a particular target.

When I get stuck, I usually try to solve the problem myself for a while, then look at documentation or examples rather than spending hours completely stuck. And I wouldn’t switch technologies too quickly. Getting far enough with one technology to build something useful teaches more than constantly starting another beginner course.

For a beginner, I’d probably choose one technology, build a small project with it, and let the project determine what you need to learn next. That gives the learning a bit more direction.