Why Your RPG Code Should Read Like a Recipe (Not a Novel)
Coffee of the day: Green Mountain Horizon Blend . Smooth, balanced, and quietly reliable, it’s the kind of roast you can drink all morning without getting tired of it. It doesn’t overpower—it just supports, giving you steady energy to do the work that matters. In many ways, it reminds me of RPG at its best: not flashy, not complicated for its own sake, but dependable and full of hidden depth when you need it. I’ve been writing RPG for over 30 years, and I’ve seen every flavor of bad code you can imagine. I’ve written most of it myself. Nested IFs seven levels deep. Variables named WK1 through WK9 . Procedures that do everything except make coffee. For years, I thought that was just how RPG worked. You had to be clever. You had to pack as much logic as possible into as few lines as possible. That was the craft. Then I became a manager. Now I spend more time reading code than writing it. And I’ve learned something that changed how I think about programming: good ...