Week one, you were unstoppable. Six-hour sessions, three tutorials a day, a notebook full of plans, and a brand new GitHub account.
Week three, you haven't opened your editor in five days. You feel guilty about it, and the guilt makes you want to avoid it even more. So now you're not just behind, you're avoiding the whole thing.
If that's you, nothing is wrong with your brain or your discipline. You just ran into the most common pattern in learning to code, and it has very little to do with talent. This post is about staying in the game long enough for the skills to stick.
1. The Boom and Bust Cycle
Almost every beginner runs the same loop:
- A burst of motivation, usually after a video or a big decision
- An intense stretch of doing far too much
- Exhaustion, or a hard concept that breaks the streak
- Guilt, avoidance, and a quiet quit
- A new wave of motivation, and back to step 1
The problem isn't step 4. It's steps 1 and 2. Motivation is a spark, not a fuel. It's great for starting and terrible for lasting. If your plan depends on feeling motivated every day, it will fail on the first bad Tuesday.
2. Think of Your Energy as a Phone Battery
Here's a picture that made this click for me.
Your focus and energy are a phone battery. Every coding session drains some. That's fine, that's what it's for. But there are two things that quietly kill the battery faster:
Background apps. Even when you're not coding, your brain is running apps: the worry that you're behind, five open courses, comparing yourself to someone your age with an internship, the endless scroll of "how I got hired in 3 months." None of it is on screen, yet all of it drains you.
Never charging. Sleep, rest days, food, walks, time with friends. These aren't rewards for finishing. They're the charger. Skip them and you're running at 5% and wondering why nothing sticks.
Staying consistent isn't about draining the battery harder. It's about never letting it hit zero, and closing the background apps.
3. Warning Signs to Watch For
Burnout tends to creep in rather than crash in. Notice if you're feeling:
- Dread when you open your editor, not just difficulty
- Everything you build feels pointless or not good enough
- Irritability or a short temper about small errors
- Trouble focusing or reading code you understood yesterday
- Sleeping badly, or replaying bugs in your head at night
- A constant background feeling of guilt about not doing enough
Catching these early is far easier than recovering from a full crash. If they're heavy, they last for weeks, or they spill into the rest of your life, please talk to someone: a friend, a mentor, a family member, or a professional. Nothing here is a diagnosis, and it's a sign to look after yourself rather than push harder.
4. Build a Minimum, Not a Mountain
The most powerful trick I know for consistency is embarrassingly simple: decide the smallest version of a study session that still counts, and never go below it.
Mine is 20 minutes: open the editor, do one small thing. Write one function, fix one bug, read one page of docs. That's a valid day.
Why it works:
- Starting is the hardest part. Once you're in, you often keep going.
- A tiny minimum removes the all-or-nothing trap. A bad day becomes a 20-minute day instead of a zero day.
- It keeps the habit alive, and habits are what get you through the months where motivation disappears.
If you want a rule to live by: never miss twice. Missing one day is life. Missing two in a row is the start of a new habit. So after a skipped day, do the minimum the next day, no matter how small.
5. Schedule It Like a Class
"I'll code when I feel like it" is the plan that fails. Give your practice a time, like a lecture you've committed to.
A sustainable pattern for a student might look like this:
| Day | Plan |
|---|---|
| Mon to Fri | 1 focused hour at a fixed time |
| Saturday | 2 to 3 hours on your project |
| Sunday | Full rest, no code |
That's about 8 to 9 hours a week. It sounds small, and it beats the 12-hour weekend binge followed by two weeks of nothing.
A few extra habits that help:
- Work in blocks. 25 minutes focused, 5 minutes break, or 50 and 10 if that suits you better.
- Look away from the screen regularly. The 20-20-20 habit is easy: every 20 minutes, look at something about 20 feet away for 20 seconds.
- Stop mid-task on purpose. End a session with the next step already written down. It makes tomorrow's start easier.
6. Close the Background Apps
You can't learn well with twelve tabs open in your head.
- One learning path. One course, one main project. Not five.
- A news diet. Checking tech news, trends, and "top 10 things to learn" every day is a distraction disguised as progress. Try once a week.
- Mute the comparison feed. If certain accounts make you feel behind more than inspired, unfollow them. You're allowed to.
- Write down the shiny ideas. New framework? New idea? Put it in a "later" list and go back to your work.
7. Track Wins, Not Hours
Counting hours makes you feel guilty when they're low. Counting wins makes you feel progress.
Keep a simple running list in your notes app:
- A bug I fixed today
- A concept that finally clicked
- Something I built and shipped
- A question I answered for someone else
Once a week, spend five minutes reviewing it: what did I ship, what did I learn, what's next? On the days when it feels like you're going nowhere, that list is proof that you are.
8. Everyone Feels Like an Imposter
That nagging feeling that everyone else understands things you don't? Almost every developer has it, including people with years of experience and impressive jobs. You only see other people's finished work, never their confusion.
You don't need to feel confident to make progress. You just need to keep showing up while feeling unsure. Confidence follows the work, not the other way around.
9. Look After the Body Running the Code
This part sounds boring and it matters more than any tool:
- Sleep. Cutting sleep to study longer is usually a bad trade. Tired brains learn poorly.
- Move. A walk, stretching, or a bit of exercise clears your head better than another hour of staring at a bug.
- Eat and drink water. It's easy to forget both during a coding session.
- Sit well. A better chair or a laptop stand can save you a lot of discomfort down the line.
- See people. Time away from screens with friends and family is not wasted time.
10. Learn With Other People
Learning alone is the fastest route to feeling isolated. Find your people:
- A study buddy you check in with weekly
- A club or community where people build things together
- An accountability partner to whom you say what you'll do this week
- Teaching others, even a beginner behind you, which cements your own understanding
Sharing what you're stuck on cuts the stress in half, and someone else's small win can pull you through a slump.
11. When You're Stuck on a Plateau
Some weeks nothing seems to improve. That's normal, because learning isn't a straight line. When it happens:
- Switch modes. If you've been watching tutorials, build something. If you've been building, read someone else's code.
- Shrink the goal. Scale down instead of quitting. One small feature this week is fine.
- Take a proper break. Two or three days fully off can do more than a week of forcing it.
Stalling is part of the process. Stopping for good is the only real failure.
12. Coming Back After a Long Break
Say you vanished for a month. Don't start with a guilty five-hour session to "catch up." That's the boom and bust cycle again.
Try a gentle re-entry instead:
- Open an old project. Just run it and see it work.
- Fix one tiny thing or add one small feature.
- Do your 20-minute minimum for a week.
- Then slowly build back up.
Nobody is keeping score of the days you missed. The only day that matters is the next one.
Tonight: Set Your Minimum
Before you close this tab, do two things. First, decide your minimum session, the smallest amount of coding that counts. Second, pick a time tomorrow and put it in your calendar.
Not a big plan. Not a new roadmap. Just a small promise you can actually keep.
The people who become good developers aren't the ones who worked the hardest in week one. They're the ones who were still showing up in month six.
Let's Connect
I'm Prayush Adhikari, currently grinding through computer engineering, leading an IT club, and building my own company on the side. I write about Linux, productivity, and the honest side of being a developer.
Tell me in the comments what your own minimum session looks like, or what usually derails your consistency. I read every one.
- LinkedIn: linkedin.com/in/adhikareeprayush
- GitHub: github.com/adhikareeprayush
- Portfolio: prayushadhikari.com.np
What should I write next: how to land your first freelance client as a student, or how to build a career network when you don't know anyone in tech?
Top comments (1)
The phone battery picture really landed for me, especially the idea of background apps draining you even when you are not coding. That worry about being behind is so real, and you named it without making anyone feel bad for having it. Calling motivation a spark instead of a fuel is something I will be repeating to people. What was the moment you personally noticed you were stuck in the boom and bust loop, and what was the first small change that actually stuck?