Hey everyone, I'm Emmanuel Olusegun, a frontend developer and aspiring full-stack dev. Originally, I wanted to study Electrical and Electronic Engineering, but I fell in love with the world of solving problems through code and programming languages—creating my own little worlds online. If you're on dev.to, you've probably battled that inner voice saying, "You're not cut out for this," especially as a self-taught learner. Self-doubt was my biggest hurdle in my first year, but it taught me invaluable lessons. In this article, I'll share my raw experiences, the frustrations, and practical tips to help you push through. If you're starting out or feeling stuck, I hope this helps you keep grinding.

The Reality Check: Why Self-Doubt Creeps In

I kicked off my self-taught journey with zero formal background—just a burning passion and a super basic setup. I started on my Itel A14 mobile phone with only 500MB RAM, using the ACode app for coding. It hung constantly, frustrating me to no end, but I was determined. I dove into resources like Goal Kickers programming books and YouTube tutorials on HTML and CSS. Building my first simple page felt like a win, but transitioning to JavaScript? That was a nightmare.

I'd forget syntax basics, loop back to the same tutorials repeatedly, and after taking tons of courses, I still couldn't build a simple website without everything breaking. Scrolling through dev communities, seeing pros share polished projects, made me question everything: "Am I even progressing?" Imposter syndrome hit hard—maybe 80% of my time was doubting myself instead of coding. But here's the truth: Self-doubt is normal, especially when learning on a shoestring setup. Recognizing it as growth pain was my first step.

Lesson 1: Set Micro-Goals to Build Momentum

Overwhelming goals killed my vibe early on. I'd aim to "master JavaScript in a week," then crash when I couldn't. The fix? Micro-goals that fit my limited phone setup.

For example:

• Day 1: Watch one YouTube video on variables and practice in ACode.
• Day 2: Code a simple alert script and tweak it.
• Week 1: Build a basic button that changes text on click.

These tiny wins built confidence, even when the phone lagged. Later, when ChatGPT gained fame, I started using it for quick explanations—like debugging why my loops weren't working. It was a game-changer for self-learners like me.

Track these in a notes app—each one quiets the doubt a bit more. Pro tip: Reward yourself, like a short break after a session, to keep the momentum.

Lesson 2: Embrace Failure as Feedback

Failure felt personal. My phone crashing mid-code (yep, it eventually died 😂) or forgetting JS concepts after hours of study made me want to quit. Parents and siblings complained about my screen time, warning me not to wreck the device, which, ironically, happened anyway. But I learned to see failures as data, not defeats.

One low point: After multiple courses, I tried building a todo list app but got stuck on array methods. I'd go back to YouTube or books, fix it, then forget again. Joining online forums helped—I'd post questions and get tips that stuck better.

Tip: Keep a "failure log" in your phone notes. Mine had gems like:

• "Forgot semicolons—always double-check syntax first."
• "Phone lag? Save code often and test in small chunks."

This mindset shift turned "I'm bad at this" into "I'm getting better."

Lesson 3: Find Your Support System

Isolation amplified my doubts, especially coding solo on a phone. My biggest motivator? My dream to one day found a company that leads in using software to solve real-world problems, like resource sharing in education.

I didn't have formal mentors, but online communities filled the gap:

• YouTube comments and dev subreddits for quick advice.
• Later, ChatGPT for personalized explanations when I felt too embarrassed to ask publicly.

No fancy accountability partners, but sharing progress mentally toward my company dream kept me going. If you're in a similar spot, lean into your "why" - it drowns out the noise.

Lesson 4: Prioritize Mental Health and Balance

Burnout was real with that lagging phone and family nagging about screen time. I'd code late into the night, forgetting to rest, which made doubt worse. My simple tip? Just try dey sleep 😔,seriously, aim for decent rest to recharge.

Other habits that helped:

• Short walks to clear my head after a frustrating session.
• Setting phone timers for focused 25-minute bursts.
• Reminding myself: Balance keeps you sane and sharp.

Your worth isn't your code output. Resting made me more effective when I did code.

Wrapping Up: You're Further Than You Think

Over the years I have grow to building projects and not just watching tutorials for hours.
Recently, I built CampuusX—a website to enhance sharing resources among students and eager learners check it out on my portfolio. I've gone from a crashing 500MB phone to frontend gigs, all self-taught. Doubt still whispers, but my dream and persistence shout louder.

If you're battling self-doubt, remember: Starting small, like I did on a basic phone, leads to big things. What's your biggest hurdle? Drop it in the comments, let's chat and maybe inspire each other.

Self-doubt isn't failure; it's feedback that you're stretching your limits.

Thanks for reading!

Emmanuel Olusegun
Founder and CEO, Algoritic Inc| emmanuelolusegun.netlify.app