Sparky's Journal

📅 April 27, 2026

How to Study the NEC

The NEC isn’t hard—I’ve just been studying it wrong.

For too long, I thought I had to memorize everything. Articles, numbers, exceptions, tables, all of it. But the more I get into real studying, the more I realize that’s not how this book is meant to be used. It’s not a memory system. It’s a lookup system.

So I changed everything.

Now I do about 30–40 lookup questions a day, but I don’t time anything. I don’t rush it. I slow everything down and actually read what the question is asking first. Not just “what is the answer,” but what situation is even being described here?

Most of my questions I build myself or pull from different places—Mike Holt questions of the day, Fast Trax system discussions, forums, random online practice questions, and even comments where people are arguing code interpretations. I don’t really care where it comes from anymore, because every question ends up pointing back to the same thing—the NEC.

Once I read the question, I break it down completely—especially multiple choice. I don’t just look for the right answer. I look at why every answer exists in the first place. Even eliminating wrong answers is part of learning because it forces me to search more deeply instead of guessing.

Then I go into the book and find it. Not by memory. By structure.

Index first. Tables next. Article layout. Definitions. Scope. Rules. Exceptions. I’m learning how the book is organized instead of trying to force it into my head.

And once I think I’ve found it, I don’t just move on. I go back and re-check everything again to make sure it actually makes sense. Because every answer is in there somewhere—it’s just about where you look and how you get there.

This method is very similar to Paul Abernathy’s 3 Wave Method, but I’m applying it in my own way.

The first wave is understanding the question itself. What is actually happening in the scenario?

Second wave is breaking down the answers and forcing myself to reason through each option using the Code, not instinct.

The third wave is confirming everything directly in the NEC and then looping back again, so I actually lock it in instead of just moving on.

But I also started realizing something else that changed the way I learn completely.

I don’t just solve problems anymore—I create them.

I take ideas from AI, from practice questions, from real installs I see, and I build my own scenarios. Because when you create the problem, you’re forced to think like the Code before you even look for the answer. You have to understand the situation, the rule that applies, and even the mistake that could happen.

That’s where the real learning happens.

Honestly, I think I’ve learned more from creating my own problems and then solving them than I ever did just grinding questions for the sake of it.

Because anyone can repeat code articles. Anyone can memorize math. Anyone can follow the steps.

But it takes something different to build a system where you’re both the one designing the problem and the one solving it.

That’s what I’m building now.

Not memorization.

A system of understanding