All video posts

Learning to code · Self-taught · Career

8 Mistakes Self-Taught Developers Make (And How to Avoid Them)

A few years ago I was a self-taught developer, excited about coding and anxious about whether it would ever land me that first job. Since then I have mentored hundreds of aspiring developers. Borrowing Charlie Munger's inversion, here is where self-taught developers fail, so you can avoid going there.

Deric YeeDeric Yee 16 November 2026 9 min read 30 min video

Prefer to read? The full article is below. Watch on YouTube.

The short version

  1. 1Becoming job-ready takes many months, not ten weeks. Plan your finances and expectations for a marathon.
  2. 2Passive tutorials feel like progress but are not. Build something small after every new concept.
  3. 3Build projects you actually care about, and rely on routines rather than motivation.
  4. 4Self-taught does not mean alone. Find a community, and keep a record of how far you have come.
  5. 5Treat the job search as a skill of its own, and do not quit. Adjust your approach instead.

Mistake 1: Believing the hype timeline

When I ask discouraged new coders what is wrong, I often hear: "I have been coding for six months and still do not have a job. Did I pick the wrong path?" A few questions later, it turns out they started because of a TikTok or an ad promising a quick route to a six-figure developer job. I fell for this too. I saw "I learned to code in 10 weeks and got hired at Google" stories and felt like a failure when I did not replicate them.

Those stories are rare exceptions. Becoming job-ready usually takes many months of consistent practice, and longer if you are learning part-time. That is completely fine. Learning to code is like learning an instrument or a new language; you would not expect to be concert-ready in a few weeks. Naval Ravikant has a line about this: the enemy of peace of mind is expectations drilled into you by society and other people.

So treat it as a marathon, not a sprint. If you are going fully self-taught and full-time, try to have savings to support you for six months to a year. That removes the "I must get a job in three months or I am out of money" panic and lets you focus on learning. And if someone online promises you a $100k developer job in a month with no background, stop following them. That is a fantasy, not a roadmap. For a realistic picture, read how long it takes to learn coding.

Mistake 2: Living in tutorial hell

Tutorial hell is spending all your time following courses and never building anything of your own. It feels like progress: hours of videos, nodding along, completing the exercises. Then you sit down to start a project from scratch and your mind goes blank.

I have been there. Early on I binged about 50 hours of a web development course and thought I had it. When I tried to build a simple to-do list on my own, I did not even know how to set up the project. I just stared at VS Code. That humbling moment taught me that passive learning is not enough. Pieter Levels, a self-taught developer turned entrepreneur, says people learn best by doing and building, and I agree completely.

The fix is to start building almost immediately. Even with 10% of a language, you can make something. After each concept, pause and apply it in a tiny project. I had a mentee who aced a popular Python course but froze when asked to build a calculator without notes. We changed his ratio: for every hour of course, two hours building something related but different. It was uncomfortable at first, but within weeks his confidence had transformed. I wrote more about breaking out in how I escaped tutorial hell.

“You shouldn't just consume, you should create.”

Deric Yee, in the video

Mistake 3: Building projects you do not care about

Even once you start building, there is another trap: the portfolio checklist mentality. You Google "projects every developer should have" and build yet another to-do app, weather app and basic e-commerce site. If you are not interested in them, you hit a motivation wall, and your portfolio looks like everyone else's.

Jason Fried of Basecamp advises scratching your own itch: build something you wish existed. For me, that eventually became Sigmaschool, because I was frustrated with traditional education. You do not have to build a startup, but you can put your interests into your projects. Love fitness? Build a workout logger. Into gaming? A score tracker or a small text-based game.

Playfulness is one of the best antidotes to burnout. On days I could not face another CRUD app, I built a silly quote generator based on a meme. Useless, maybe, but it made me smile, and I learned to fetch and display API data. As an employer, after the tenth weather app they all blend together. The candidate I remember built an inventory tracker for his family business, because it was real and he had a story to tell. Finishing projects matters more than polishing them.

Mistake 4: Relying on motivation instead of discipline

Motivation is the spark that gets you started, that 2am "I am going to change my life" energy. But it is a sugar rush. Some days the novelty has worn off, or you hit a nasty bug yesterday and dread facing it. Miss one session, then another, and soon coding becomes something you will "get back to someday". The people who make it are not always motivated. They have built habits that work regardless.

01

Book coding time like appointments

Pick fixed slots, say Monday, Wednesday and Friday from 7pm to 9pm, put them in your calendar and tell the people you live with. Structure frees you from waiting to feel like it. Action often comes before the feeling.

02

Log progress and celebrate small wins

Keep a simple log of each session. Looking back over a month of notes is motivating in a way that lasts, like seeing gains at the gym.

03

Look after your body

Four hours of sleep, three coffees and no water is a recipe for disaster. Sleep, hydrate and move.

04

Rest, do not quit

When you are exhausted, a short break or a brisk walk beats staring at a screen for five hours and feeling guilty. Do not brute-force it either: a 14-hour day every day is not sustainable.

Mistake 5: Going it alone

The self-taught path can be lonely: you, a laptop, a dark room and endless Stack Overflow searches. You will get stuck on things someone else could solve in five minutes, and with nobody to ask you can spin your wheels for days. At first I was too proud, or too shy, to ask for help. I thought real programmers figured it out alone. Wrong. Real programmers ask for help all the time; they just know where and how.

Once I joined a few Discord and Slack communities, and later built a community at Sigmaschool, my learning accelerated. Peers on the same path share tips, vent about errors and celebrate wins. There are plenty of online options, from freeCodeCamp to Reddit's learn programming community. One tip: introduce yourself and contribute before asking. People help those who engage sincerely, not drive-by askers.

A mentor can be a game changer too. Even one 30-minute call where someone experienced reviews your code or CV can save you weeks. And do not compare yourself harshly with others. Someone posting a job offer after six months is inspiration, not a stick to beat yourself with. Everyone learns on a different timeline.

Mistake 6: Not recognising your progress

When you teach yourself, there are no grades, no teacher saying "good job, you moved up a level". You have to be your own coach, and if you never take stock, you may wrongly conclude you have learned nothing. That belief makes people quit.

A simple exercise: open something you coded one or two months ago. You will probably cringe, which is fantastic, because it means you have improved. Progress is gradual, like a puppy growing; you only notice from an old photo. So keep your old code as a trophy. I still have my first website, which was hideous and mostly copy-paste. I also kept a list of milestones and a map of what I knew and what was next. Each tick was a confidence boost. A lack of perfection is not a lack of progress.

Mistake 7: Treating the job search as an afterthought

After a long learning journey you want your reward, but the job search is a new challenge that needs the same strategy. Make your projects accessible: deploy them and link your GitHub on your CV. Hiring managers lose interest fast when they only see project names with no links. List skills you actually know, not 50 technologies. Present projects professionally under experience. A short, customised cover letter can still help a junior applicant stand out.

Apply broadly and expect rejection. When I first job hunted in tech, I sent out nearly 300 applications. Most were black holes, some were polite rejections, a handful became interviews and one worked out. You only need one yes. Make it systematic: say five applications every weekday, tracked in a spreadsheet, with follow-ups. Prepare for interviews like any other skill, including some algorithm practice if the role has coding challenges. Our tech interview guide is a good place to start.

Mistake 8: Giving up too soon

The only guaranteed way to fail is to stop. I have seen promising learners quit right before they turned a corner, like the miner who stops one swing from the diamonds. You do not need to be a genius; I am certainly not. You need to be relentless and adaptable. Perseverance is not repeating what is not working. If 100 applications produced no interviews, step back: is your CV effective, are you targeting the right roles, should you network more?

I hit a low point myself. After months of coding alone I felt like an imposter and nearly shelved the whole idea. What saved me was everything above: talking to friends and mentors, looking back at old projects, and realising I was comparing myself with people who had four-year degrees. I gave it one last push and built one of my best projects, which became a cornerstone of my portfolio. If I had quit a week earlier, the story would have been "I tried coding but it did not work out".

If skeptical family keep asking when you will get a job, remember you are driving the bus. You do not owe anyone an overnight success. Keep your head down and keep improving. As Brad Jacobs puts it, so much of success comes from keeping your head in a good place. If you would like structure, mentors and a community on this journey rather than doing it alone, try the free trial and see how we teach at Sigmaschool.

“You are probably closer to success than you think.”

Deric Yee, in the video

Questions people ask

  • How long does it take a self-taught developer to become job-ready?

    Usually many months of consistent practice, and longer if you are learning part-time around a job. Stories of people getting hired after ten weeks are rare exceptions. If you are studying full-time without income, aim to have savings for six months to a year so financial panic does not push you to quit or rush before you are ready.

  • How do I get out of tutorial hell?

    Start building as soon as you learn each concept. After a tutorial section, pause and apply the idea in a small project of your own that the instructor did not walk you through. A useful ratio is one hour of course content to two hours of building something related but different. The struggle of getting stuck and searching for answers is where the real learning happens.

  • How do I stay consistent when I am not motivated to code?

    Rely on routine rather than motivation. Book fixed coding slots in your calendar and treat them like appointments, tell the people around you, and keep a simple log of what you did each session. Often motivation arrives after you start. Look after sleep, water and exercise, and when you are exhausted, take a short break rather than quitting.

  • Is it normal to get lots of rejections as a junior developer?

    Yes. Junior roles are competitive, and many applications get no response at all. I sent nearly 300 applications on my first tech job hunt before one worked out. Treat it as a system: a set number of applications a day, tracked in a spreadsheet with follow-ups. If nothing converts after a large batch, change your CV, targeting or networking.

Your next step

Our 12-week AI-Native Software Development Programme is a live, mentor-reviewed cohort where you build and ship real products with AI, and learn to explain every line. Start with the free trial to see how we teach, then decide.

Watch next

All videos

Learn the fundamentals that pay off in any direction.
Coding plus AI, taught properly.

Whatever you end up doing, the people who understand how software and AI actually work get to direct them. Try the first lessons free, no card needed, or see the full 12-week AI-Native Software Development Programme.