3 ms·
Hm, so for that, I think find the "process loop." That is, the equivalent of the edit-compile-test cycle for Magic. For example, first choose your domain scope
by turtleyacht 3y ago
Hm, so for that, I think find the "process loop." That is, the equivalent of the edit-compile-test cycle for Magic.
For example, first choose your domain scope: a thematic deck, super-crunchy probabilities, or studying a pro former deck?
And then create a deck. That's the edit step.
From here, try shuffling and drawing different initial hands. This could also be done in a program, so it could be a good chance to code something.
Finally, some way to test the deck by playing online.
Iterate by repeating the cycle, refining the steps, and so on.
- dottjt 3y agoInteresting, thank you for that. What are your thoughts on documentation separate from the activity itself? Do you see it as something useful, or how do you go about approaching that?
- turtleyacht 3y agoIt's easiest to document alongside the activity, or keep a journal. Otherwise, it may never get done. At least with code, the commit and docs let me repeat info twice, but not a straight copy-paste. The commit lets me discuss why vs how and technical details; the docs answer things like * I forgot everything; how do I onboard myself? * Common tasks * Troubleshooting Preferences vary. I just know I'll forget if I'm not writing it down in the moment.