Bill Zebub
“It’s probably Matt Mercer’s fault.”
I don't know how this thread got from "easy to read/prep" to "lazy GM". Maybe I missed the progression.
But it does occur to me that what we are calling "preference" might be more about wiring differences. In the old MapQuest days I used to ask people if they could only take half of the instructions, the written steps or the map with the route drawn on it, which would they take? NOBODY that I asked had trouble choosing; they knew which one they actually used to navigate. (I'm 100% in the Map category; I would not even look at the written part.)
Similarly, I really struggle with written recipes. I will look back and forth between my cooking and the recipe multiple times for each step. Then somebody pointed me at cookingforengineers.com, and I could glance at one of their recipe diagrams and think, "Oh, ok. Got it."
As a programmer I still really like flow charts. Even if I don't draw them anymore, I still "see" them while coding. And, for that matter, I pretty much learned to program by writing a graphics library for data visualizations because I would rather see data than read it.
So while I still enjoy reading a great story, or great writing in general, if I want to wrap my head around a complex adventure module, I want it in a highly structured format that strips out unnecessary text.
But it does occur to me that what we are calling "preference" might be more about wiring differences. In the old MapQuest days I used to ask people if they could only take half of the instructions, the written steps or the map with the route drawn on it, which would they take? NOBODY that I asked had trouble choosing; they knew which one they actually used to navigate. (I'm 100% in the Map category; I would not even look at the written part.)
Similarly, I really struggle with written recipes. I will look back and forth between my cooking and the recipe multiple times for each step. Then somebody pointed me at cookingforengineers.com, and I could glance at one of their recipe diagrams and think, "Oh, ok. Got it."
As a programmer I still really like flow charts. Even if I don't draw them anymore, I still "see" them while coding. And, for that matter, I pretty much learned to program by writing a graphics library for data visualizations because I would rather see data than read it.
So while I still enjoy reading a great story, or great writing in general, if I want to wrap my head around a complex adventure module, I want it in a highly structured format that strips out unnecessary text.