My Tech & Coding Journey

my-tech-&-coding-journey

I wasted 1 full year learning how to code… and I didn’t even know it.

Every night I’d open YouTube…
“JavaScript for beginners.”
“Build Netflix clone in React.”
“Top 10 VS Code extensions.”
I felt busy. I felt like I was progressing.

But guess what?

I couldn’t build anything on my own.
Not a single working app — without checking a tutorial every 5 seconds. 😩

Looking back now, I realized I was making 3 major mistakes that almost every self-taught dev makes 👇🏽

💀 Mistake #1: Tutorial Hell
I was watching videos like Netflix.
I thought “learning” was the same as “doing.”
Biggest lie ever.
▶️ Play. Pause. Copy. Paste.
But the moment I tried to build alone — nothing worked.

✅ What I changed:
I started building without watching. Broke stuff. Googled errors. Struggled.
THAT’S when I actually became a developer.

📍 Mistake #2: No Clear Roadmap
I was learning React before understanding JavaScript.
One day I’d study Node.js. The next day I’m trying to learn Python.
I was busy, but I wasn’t moving forward.

✅ What I changed:
I picked ONE stack.
I mapped out the order:
→ HTML → CSS/SASS → JavaScript → PHP/MySQL → Node.js → Python
No distractions. No hopping.

📦 Mistake #3: Useless Projects
I had 4 projects on GitHub.
To-do app, calculator, weather app, and another to-do app 😅
None of them proved I could solve real problems.

✅ What I changed:
I built apps that solved actual problems.

  • A blog system with user auth.

  • App Clone.

  • A dashboard.

  • A job tracker.

  • JobHunt Web + App

Projects that showed I was hireable, not just “learning.”

If you’re self-taught and stuck…
You’re not lazy. You’re not dumb. You’re just making these same mistakes.

But you can fix it:

🔁 Stop watching endlessly
📌 Follow a plan
🛠 Build like your future depends on it — because it does

It took me a full year to figure this out.
I hope it saves you that time.

Now I a FullStack Developer with 4-5 years experience.

You’re not too late.
You’re just one shift away. 💻

Save for later ❤️

©️ Ekopteach ©️ Ekop Designz Hub ©️ Favour Ekop

Total
0
Shares
Leave a Reply

Your email address will not be published. Required fields are marked *

Previous Post
developer-tooling-#007

Developer Tooling #007

Next Post
rick-beato:-the-concepts-that-actually-changed-my-playing

Rick Beato: The Concepts That Actually Changed My Playing

Related Posts

AI治理最重要的能力:缺乏证据支持时懂得暂停

1)观点先行(P0) 一句话观点: 在 AI 协作里,最有价值的治理能力不是“更快修完”,而是“证据不够时敢停下,并把缺什么证据说清楚”。 2)治理背景(P1) 复杂系统里的真实问题,不是没人干活,而是大家都在干活,却很难判断到底有没有真的完成。 AI 参与后,这个问题会更明显: AI 很容易给出“看起来已经完成”的答案。 多个智能体并行提交回执,信息会很快变成噪音。 模块测试通过,常常被误读成系统已经恢复。 本地治理体系之所以更快,不是因为流程更短,而是因为它把“没完成”这件事制度化了: 可以停在中间状态。 可以明确写出阻断原因。 可以等证据补齐后再推进状态。 3)信号提取(P0)…
Read More