Forem: Mark Justin Superable

Learning Principles to Help You Learn Faster and Smarter if You Want to Become a Dev in the AI Age

Mark Justin Superable — Tue, 23 Sep 2025 07:00:10 +0000

We’re living in the AI age. Information is growing at exponential speed, and the ability to learn faster, adapt faster, and retain more knowledge can set you apart as a software developer.

But here’s the catch—most people still study wrong.

If you’ve been:

rereading textbooks 📚
rewatching tutorials ▶️
highlighting notes in rainbow colors 🌈
rewriting notes just to make them look aesthetic…

I hate to break it to you—those are passive study methods. They drain your time and energy without bringing you closer to becoming an effective developer.

In this guide, we’ll rewire your learning strategy using principles I’ve picked up from:

Ultra Learning (Scott H. Young)
Atomic Habits (James Clear)
The Only Study Guide You’ll Ever Need (UnJaded Jade)
Ali Abdaal & other YouTube creators

So you can learn deeply, retain concepts long-term, and apply them in real coding scenarios.

🔪 Stop Comparing Study Hours

We’ve all met someone who proudly says:

“I studied for 10 hours yesterday.”

But then they get the same—or worse—results as you.

That’s because time spent ≠ knowledge gained.

Think of it like this:

Lumberjack A chops trees with a dull axe → lots of effort, little progress.
Lumberjack B sharpens his axe first → then cuts through trees with ease.

💡 Be like Lumberjack B. Don’t obsess over marathon hours. Sharpen your tools first.

And remember: learning is personal. Comparing your hours to others only creates guilt and burnout.

⚙️ Systems > Goals

Most beginners say:

“I want to be the top developer.”

That’s a goal. But here’s the truth:

Goals don’t get results—systems do.

From James Clear’s Atomic Habits:

Goal: “I want to get fit.”
System: Go to the gym 3x a week, increase weights, track sleep and food.

For developers:

Goal: “I want to learn data structures.”
System: Solve 3 coding challenges daily, explain 1 concept weekly, review mistakes.

🚀 Build systems that make progress inevitable. The results will follow.

🧩 The SAAD Framework (Jade Bowler’s Method)

From The Only Study Guide You’ll Ever Need:

Spaced Repetition → Review concepts at intervals (syntax, algorithms, formulas).
Active Recall → Quiz yourself. Use flashcards, LeetCode, or explain from memory.
Association → Link abstract concepts with analogies. (Recursion = Russian nesting dolls).
Desirable Difficulty → Practice just beyond your comfort zone. Hard enough to stretch, not so hard you quit.

🛠 Proven Study Methods for Developers

Feynman Technique → Teach a concept like you’re explaining it to a child—or your rubber duck.
Blurting → Close notes, write everything you recall, then check gaps.
Past Paper & Project Work → Stop hoarding tutorials. Build small apps and code from scratch.

⏳ Optimizing Your Time

Parkinson’s Law → Work expands to fill the time you allow. Set shorter deadlines.
Eat the Frog → Do your hardest task first (debugging, tough algorithms).
Retrospective Timetables (Ali Abdaal) → Track what you actually studied, not what you planned. Use color codes: 🔴 red (weak), 🟡 yellow (okay), 🟢 green (confident).

⏱ Use time as a tool, not a trap.

🧠 Memory Tricks That Work

Memory Palace → Place coding concepts in familiar locations. (Recursion in the fridge = keeps repeating).
Mnemonics & Acronyms → Example: CRUD (Create, Read, Update, Delete).
Imagery & Storytelling → Turn abstract concepts into vivid images.

🎯 Deep Work vs Pomodoro

Pomodoro (25-min sprints) → Great for getting started.
Deep Work (90+ mins) → Where breakthroughs happen.

💡 Reward wisely. Don’t break focus to scroll TikTok—stretch, snack, or walk instead.

💥 When You Fail (And You Will)

You’ll bomb coding challenges. Misread algorithms. Sometimes even AI will outshine you. That’s normal.

Failure = data.

Keep a bug journal or wrong answers list. Review, adapt, grow.

🏀 Michael Jordan missed thousands of shots. That’s why he succeeded.

🐢 Dealing with Procrastination

Procrastination isn’t always laziness. Often it’s because:

You’re avoiding discomfort.
You’re overwhelmed and don’t know where to start 🥺

Hacks:

Make tomorrow easy. Start with something tiny (“Open VS Code. Write a few lines.”). 1% daily > 0%.
Allow a 10-min procrastination window. Promise yourself you’ll start after.
Beware of “productive procrastination.” Watching coding videos ≠ coding.

✅ Quick Recap: 5 AI-Age Learning Principles

Active Recall > Passive Review → Test, don’t just reread.
Systems > Goals → Build habits, not wish lists.
Spaced Repetition → Don’t cram—revisit over time.
Deep Work > Multitasking → Focus is your superpower.
Failure = Feedback → Mistakes are growth signals.

🌟 Final Thoughts

Learning software development in 2025 isn’t just about Python, React, or AI tools.

It’s about building the right mindset and systems to outpace the flood of information.

Sharpen your study habits now, and you’ll slice through challenges later—like a sharp axe through butter. 🪓🧈

Follow Me:

-LinkedIn: MarkJustin

-GitHub: CosmicErased

-Twitter: Marky-Tech

Beginner Dev Mistakes I Made (and What I’m Doing Differently Now)

Mark Justin Superable — Fri, 19 Sep 2025 07:45:02 +0000

Note:
Tips can be applied to any specialization, not only web dev.

When I started learning to code, I chose a web dev specialization. I thought the fastest way to “become one” was to dive straight into all the flashy frameworks and tools. React, Tailwind, GSAP—you name it, I tried it. The problem? I was rushing ahead without a solid foundation in plain HTML, CSS, and JavaScript.

I’m sharing this because I know a lot of beginners go through the same struggles. Maybe you’re stuck in tutorial hell, chasing the “perfect” roadmap, or comparing yourself to others. I’ve been there, and here’s what I’ve learned (and what I’m doing differently now).

🚩 1. Rushing Into Tools Without Foundations

I thought learning React right away would make me a “real developer.” But without knowing core web fundamentals, I was just copying code I didn’t fully understand.

What I’m doing now: I slowed down and committed to The Odin Project. It focuses on the basics before moving into advanced topics. That strong foundation gives you transferable skills—whether you go into web dev, data, AI, or apps.

🚩 2. Getting Lost in Tutorial Hell

We’ve all been there: jumping from one tutorial to another, copying projects, never finishing anything. It feels like progress, but it’s not.

What I’m doing now: I literally closed YouTube for a while. No more flashy thumbnails promising shortcuts. Instead, I focus on building projects on my own, even small ones. Struggling through mistakes teaches more than following along passively.

🚩 3. Waiting for the “Perfect Plan”

Another mistake: trying to find the best resource, the perfect roadmap, or the “ultimate way” to learn. I wasted more time researching than actually coding.

Lesson learned: There is no perfect plan. Just start. Pick one resource and stick with it. Momentum matters more than perfection. You’ll adjust as you go.

🚩 4. Fighting Imposter Syndrome

Imposter syndrome is real. It whispers: “You’re not good enough. You’ll never catch up.”

What keeps me going: I remind myself that even senior developers are still learning. That’s the beauty of this field—learning never stops. If you love what you’re doing, the results will show.

💡 Final Advice to Beginners

Enjoy the process.
Ask for help when you’re stuck.
Don’t wait for the perfect plan—just start.
Pick one specialization (web, data, AI, cyber, apps).
Build a strong foundation in core skills before chasing frameworks.

The journey isn’t about racing to “full stack in 6 months.” It’s about loving what you build, embracing mistakes, and growing one step at a time.

💬 What about you? Have you been stuck in tutorial hell or jumped too fast into new tools? I’d love to hear your story in the comments.

Follow Me:

LinkedIn: MarkJustin
GitHub: CosmicErased
Twitter: Marky-Tech

How I’m Learning to Code in the AI Age (2025-2026 Edition)

Mark Justin Superable — Tue, 16 Sep 2025 07:46:27 +0000

To all beginners out there — I’m on the same path as you. Learning to code in 2025 feels… different. AI tools like ChatGPT and Copilot are everywhere. Sometimes they help me, sometimes they confuse me.

Here’s what’s working for me as a beginner, and how I try to learn without getting stuck or frustrated.

1. Start Small and Get Coding Fast

→Pick a short tutorial you can finish:

Example: A YouTube crash course on the language you want to learn.

Why: Short tutorials let you start coding immediately. Long ones can make you watch forever without doing anything — just another video to “watch later.”

→Follow it step by step, then try it on your own:

Example: Copy what the tutorial does first. Then close it and build the project yourself.

Why: Doing it yourself helps you remember better and is a form of active recall.

→Make small changes the third time:

Example: If you’re building a to-do list app, change colors, sizes, or add a new feature.

Why: This makes the project your own and helps you understand it more deeply.

→Ask AI if you get stuck:

Example: If your code doesn’t work, ask ChatGPT, “Why is my to-do list not working?”

Why: AI can help you move forward without giving the answer directly, so you still learn by doing.

2. Build and Learn as You Go

→Mini-projects are your best friend:

Example: Build a calculator, a simple website, or a personal project.

Why: Building projects helps you remember and understand concepts faster than just watching tutorials.

→Learn concepts when you need them:

Example: Don’t know what a “function” is? Look it up or ask AI while coding.

Why: Learning just-in-time keeps you moving and avoids overwhelm.

→Make it personal and fun:

Example: Create a website about your favorite hobby or a small tool for yourself.

Why: Projects that interest you are more fun and easier to stick with.

→Try the reverse advance method:

Example: Start learning React even if you only know a little JavaScript. Learn the basics as you build.

Why: You learn two things at once and reach bigger goals faster than sticking strictly to beginner content.

3. What to Avoid as a Beginner

→Long tutorials (>2 hours):

Why: They can trap you in “tutorial hell” — watching without coding.

→Endless notes without understanding:

Why: Notes don’t help if you can’t apply them in a project.

→Copying code just to finish:

Why: You only learn when you experiment yourself.

→Hunting for the “perfect” tutorial:

Why: There isn’t one. The best way is to start coding now.

4. Quick Check for Yourself

Before moving on, ask:

✅ (Can I write this code myself?

✅ (Do I understand what I just did?

✅ (Could I explain it to a friend with no coding experience?

If the answer is no, go back and try again. It’s slower, but you learn better this way.

💡 Takeaway:
I’m just a beginner, and I’m still figuring things out — just like you. The goal isn’t perfection. It’s trying, experimenting, and repeating. AI is a helper, not a replacement. Step by step, project by project, you’ll slowly learn to code and understand it.

Follow Me:

LinkedIn: MarkJustin

GitHub: CosmicErased

Twitter: Marky-Tech