There is a moment in every campaign when the world stops being something you observe and starts becoming something you influence. Up to this point, I had been shaping structure and appearance. The terrain existed. The armor was in place. The realm looked complete, but it did not yet respond. It waited. JavaScript is where that waiting ends. When I first stepped into this part of the stack, I realized something subtle but important. The browser is not just rendering a page. It is executing a sequence of instructions. It reads, evaluates, and moves forward through time. That sense of progression, of one thing happening after another, is the foundation…
-
-
Every campaign begins with a map. Not a perfect one or a complete one, but something reliable enough to take the first step without walking straight off a cliff. That is exactly how I learned to approach the browser, not as a mystery box, but as terrain that can be studied, understood, and navigated with intent. When I first started learning web development, I believed the map was the code itself. HTML, CSS, and JavaScript felt like the ground beneath my feet. If I could write them well, I assumed the world would simply appear the way I imagined it. It took some frustrating and very humbling moments to realize…
-
When I started teaching, I thought my job was to know the material. Know it cold. Know it forward and backward. Be ready for every question. What I learned instead is that knowing something and explaining something are two very different skills. That realization followed me back into software development. In the classroom, I could solve a problem in my head in seconds. But when I tried to explain it the same way I solved it – jumping steps, skipping assumptions, compressing logic – I would lose half the room. The students weren’t confused because the material was impossible. They were confused because I had teleported from A to D…
