Introduction

Someone once asked me to teach them how to program. They didn't care which language. They just wanted to learn how to think like a programmer. That question sent me back to my own beginning: a hand-me-down Tandy TRS-80, no hard drive, no disk drive, just a manual and its BASIC dialect built in. I read that manual cover to cover and knew everything the language could do. That completeness is what modern learners have lost. Today's languages aren't harder to learn because programming got harder, they're harder because they got wider. Libraries, paradigms, and tooling choices stack up before a beginner ever writes their first real line. I looked at reviving an old BASIC dialect to recreate that narrow, learnable scope, but those languages don't transition well into what people actually use today. So I built QF Code instead, modern enough to lead somewhere, narrow enough to finish the manual.

Designing QF Code put me back in touch with the fundamentals in a way I hadn't been in years. Every decision about the language, what to include, what to leave out, forced me to think hard about how I'd actually teach each concept. I started taking notes, just for myself, just to organize my own thinking. At some point I realized I had enough material to put together a short guide to help me teach. Then, somewhere along the way, I looked at what I'd written and realized it wasn't a guide anymore. It was a book. So I changed direction and finished it as Underneath the Syntax.

When I teach, I reach for real-world objects and analogies, and I draw a lot of pictures. Being able to visualize how something works is half the battle. My first goal isn't mastery. It's understanding. The material becomes much less intimidating once it is approached in the right order. The real work of coaching someone is helping them make that jump, the moment where the dots connect and they suddenly see why a keyword or a command exists at all, not just what it does. I remember exactly when that happened for me with arrays. I was confused about the point of them. Why not just use separate variables if you had more than one thing to store? It didn't click until I saw an array paired with a FOR...NEXT loop. That was the moment I understood the power of it, not from a definition, but from watching the two ideas work together. This book is built around giving you moments like that, on purpose, one after another.

You will not spend this book writing a series of unrelated five-line examples. We will build one program together, starting with a few lines of output and growing it as each new idea becomes useful. Variables, loops, arrays, functions, error handling, and the rest will appear because the project needs them, not merely because they are next on a checklist.

This handbook is for anyone who wants to learn programming through QF Code and understand how the language's pieces work together. If you've never programmed before, it will take you from your first line to a complete working project. If you already know how to program, it will help you become fluent in QF Code quickly.

I never had anyone build that experience for me. I had a manual, a computer, and a lot of trial and error. You have something I did not: a language, an IDE, and a path designed specifically to create those moments of understanding. Not simplified because you can't handle complexity. Simplified because you deserve to actually understand what you're doing before anyone piles more on top of it. Turn the page. Open the IDE. Type your first line. That's really all it takes to start.

---