Skip to main content

Rebuilding JavaScript Fundamentals in 100 Days: Why I'm Going AI-Free

A practical roadmap for relearning JS from the ground up, and why heavy AI tool usage quietly erodes core developer skills

Updated 3 min readMarkdown
Part of series100 Days of JS Fundamentals
Rebuilding JavaScript Fundamentals in 100 Days: Why I'm Going AI-Free

TL;DR: After two years of leaning on AI coding tools, I noticed my fundamental problem-solving speed had dropped. I'm spending the next 100 days relearning JavaScript from scratch with zero AI assistance. Here's the roadmap and the reasoning behind it.

The trigger

A minor array transformation bug in a client project took me several minutes to diagnose manually. Two years ago, this would have been instant. The gap wasn't knowledge, it was atrophied recall. Closures, scope, the event loop, concepts I once reasoned through automatically had become things I let autocomplete handle.

This is a known pattern, not just a personal failing. When a cognitive task is consistently offloaded, the underlying skill weakens from disuse. AI coding assistants are exceptionally good at hiding this until a moment forces the gap into view.

The constraint

For 100 days, no Cursor, no Copilot, no ChatGPT for the learning itself. The goal isn't to reject AI tools permanently. It's to rebuild the baseline skill so AI becomes a multiplier again, not a replacement.

The roadmap

Week 1 to 2: Array methods (map, filter, reduce) and higher order functions. The daily-use building blocks that are easy to use correctly via autocomplete and easy to misunderstand structurally.

Week 3: Closures and scope. Specifically, the backpack model, why an inner function retains access to outer variables after the outer function has returned, and how the scope chain resolves lookups.

Week 4: Call stack, Web APIs, callback queue, and the microtask queue. Tracing execution order for setTimeout vs Promise.then() by hand, not by running it and guessing.

Week 5: Promises and async/await, including the two-step nature of fetch() (response object, then .json()), and why response.ok checks matter since fetch doesn't reject on HTTP error codes.

Week 6: OOP, classes, constructors, this binding, inheritance via extends, super(), and method overriding (polymorphism). Also documented a classic trap: this.count = this.count++ silently fails to increment, because post-increment returns the old value before incrementing.

Week 7 to 8: Error handling, modules, and a final project built without AI assistance.

After week 8: React, Node.js, MongoDB, then system design, treating it as the layer most developers attempt before the foundation underneath is solid enough to support it.

Why this matters beyond personal discipline

There's also a practical argument here, not just a skill one. Token costs for AI tools are likely to rise over time, and free tier access is likely to shrink as providers optimize for margin. Local AI is frequently proposed as the long-term alternative, but it requires RAM, GPU, and bandwidth budgets that most working developers, especially outside major tech hubs, don't have. Strong fundamentals are the one asset that doesn't depend on tool pricing or infrastructure access.

What's next

Each week going forward, I'll publish a focused technical breakdown of that week's core concept, written the way I wish it had been explained to me, with the actual mistakes and corrections included. Closures first, then the event loop, then promises.

If you're a developer who's noticed a similar erosion, or you're earlier in your career and want to build strong fundamentals before AI tools become your default, follow along.

2 views

About the author

  • Full Stack Developer based in Sylhet, Bangladesh, working with React, Next.js, and WordPress/WooCommerce since 2023. Currently spending 100 days rebuilding my JavaScript fundamentals from scratch, completely AI-free, after noticing heavy reliance on AI coding tools had quietly weakened my core problem-solving skills. I write technical breakdowns of concepts as I relearn them (closures, the event loop, promises, OOP) along with honest reflections on what AI dependency costs a developer long-term. Open to remote opportunities and always happy to connect with other developers thinking about the same tradeoffs.

No comments yet. Be the first to comment.

100 Days of JS Fundamentals

Part 1 of 1

After two years of leaning on AI coding tools, I noticed my fundamental problem-solving speed had dropped. I'm spending the next 100 days relearning JavaScript from scratch with zero AI assistance. Here's the roadmap and the reasoning behind it.