Learning something hard follows a pattern. Whether you are building your first website, writing your first Python program, or making your first dashboard, you will move through the same four stages: a messy start, a discouraging middle, quiet growth, and a moment of gratitude when you look back. Knowing the pattern will not remove the difficulty, but it makes it much easier to keep going. Here is what each stage looks like and what to do in it.
Stage 1: The messy beginning
Your first attempt at anything will look bad. The website with crooked buttons. The program that crashes on line three. The Canva design where nothing lines up. That is not failure. It is the process, and every mistake hands you something specific to fix.
Writers have known this for decades. Author Anne Lamott, in her well-known essay on first drafts from Bird by Bird, argues that good writers all produce rough early drafts, and that those drafts are what make the better versions possible.
What to do at this stage:
- Finish the ugly version. Run it, publish it, or show it to one person.
- Do not compare your rough draft to someone else's finished work. They had a messy start too. You just never saw it.
If you want a guided place to make that first rough attempt, CodeDevPay Academy has free beginner courses such as Python Zero to Hero, Web Development Foundations, and Canva 101.
You can't skip the messy part, and you don't need to.
Stage 2: The messy middle
Then the excitement fades. Errors stop making sense. Tutorials that felt easy now assume things you have not learned yet, and you start wondering whether you should quit.
Beginnings are exciting because everything is new. Endings feel rewarding because you can see what you built. The middle is where you actually struggle, and that is normal, not a red flag.
Radio host Ira Glass describes this as a gap between your taste and your skill. You started because you have good taste, so you can tell your work is not good yet, and many people quit right there. His advice is to expect the gap to last for a couple of years and to close it with a large volume of work rather than waiting to feel ready.
Learning research points the same way. Psychologists Elizabeth and Robert Bjork argue that how well you perform right now is not a reliable measure of how much you are learning. They also show that certain difficulties, such as spacing out your practice and testing yourself instead of rereading, improve long-term learning. So the afternoon you spent fighting one bug and barely moving forward may still have been doing real work.
What to do at this stage:
- Shrink the goal. Fix one error or finish one function instead of the whole project.
- Come back tomorrow. Spaced practice beats one exhausting marathon.
- Ask for help early, and describe what you already tried.
- Follow a structured course so you always know what comes next. On the Academy, JavaScript Mastery From Beginner to Pro is one to reach for when the basics start getting harder.
The person who becomes good at something isn't the one who never struggled. It's the one who kept going while struggling.
Stage 3: Growth you don't notice
Growth is quiet. Nobody announces it. It looks like finally understanding something that confused you weeks ago. It looks like reading an error message and knowing where to look. It looks like opening a blank file with a little less dread, or having the confidence to try again after a failed attempt.
The unfinished projects, the late nights, and the topics you had to learn twice were not signs you were stuck. They were part of the process.
Because progress is so easy to miss, make it visible:
- Save your early work so you can compare it with what you make now.
- Once a week, write down one thing you understand today that you did not a month ago.
- Choose courses that track your progress. CodeDevPay Academy courses can include quizzes, projects, badges, and certificates, so your growth leaves a record.
Some day you will read that list and think: I was growing the whole time.
Stage 4: The chapter you'll be grateful for
Some chapters only make sense in hindsight. The course you almost skipped. The skill you were scared to learn. You often do not recognise a chapter's importance until you are standing in the next one.
Steve Jobs made this point in his 2005 Stanford commencement address. He described a calligraphy class he took with no practical purpose in mind. Ten years later, it shaped the typography of the first Macintosh. His conclusion was that you cannot connect the dots looking forward, only looking back.
That is why the hard thing in front of you deserves patience. Think of the course you keep scrolling past, and open it this week. The chapter you were so afraid of was always going to become your favourite.
One story, not four
Start, struggle, grow, look back. These are not four separate experiences. They are one continuous story, and the discomfort at each stage is proof that you are moving through it, not stuck.
If you are in the middle right now, keep going. Pick one small thing to finish today, and start your next course at CodeDevPay Academy.
References
- Anne Lamott, essay on first drafts from Bird by Bird (1994), reprinted by Brandeis University Writing Program: https://www.brandeis.edu/writing-program/shitty-first-drafts.pdf
- Ira Glass on the gap between taste and skill, with transcript, via kottke.org: https://kottke.org/20/12/the-gap-between-having-good-taste-and-doing-good-work
- Elizabeth L. Bjork and Robert A. Bjork (2011), "Making Things Hard on Yourself, But in a Good Way: Creating Desirable Difficulties to Enhance Learning," UCLA Bjork Lab: https://bjorklab.psych.ucla.edu/wp-content/uploads/sites/13/2016/04/EBjork_RBjork_2011.pdf
- Steve Jobs, 2005 Stanford Commencement Address, full text via James Clear: https://jamesclear.com/great-speeches/2005-stanford-commencement-address-by-steve-jobs
- CodeDevPay Academy, course catalogue: https://academy.codedevpay.com/courses/
Comments