Dan Q
I’m testing a handful of highly-experimental new features on my personal website using multivariate (“A/B”) testing.
If you visit within the next day or so you’re likely to be randomly-selected to try out one of them. (If you’re not selected, you can manually enable one of the experiments.)
I’d love to hear your feedback on these Very Serious New Features! Let me know which one(s) you see and whether you think they should become permanent fixtures on my site.
When geocachers find a geocache, they typically “log” their find both in the cache’s paper logbook and on one of the online listing sites on which the cache’s coordinates can be found.1
I’ve been finding and hiding geocaches for… a long while, so I’ve seen lots of log entries from people who’ve found my caches (and those of others). And it feels to me like the average length of a geocaching log entry is getting shorter.
“It feels to me like…” isn’t very scientific, though. Let’s see if we can do better.
To test my hypothesis, I needed a decade or so of logs. I didn’t want to compare old caches to new caches (in case people are biased by the logs before them) so I used Geocaching.com’s own search to open the pages for the 500 caches closest to me that are each at least 10 years old.
I hacked together a quick userscript to save all of the logs in a way that was easier than copy-pasting each of them but still didn’t involve hitting Geocaching.com’s API or automating bulk-scraping (which would violate their terms of service). Clicking each of several hundred tabs once every few minutes in the background while I got on with other things wasn’t as much of an ordeal as you might think… but it did take a while.
I mashed that together into a CSV file and for the first time looked at the size of my sample data: ~134,000 log entries, spanning 20 years. I filtered out everything over 10 years old (because some of the caches might have no logs that old) and stripped out everything that wasn’t a “found it” or “didn’t find it” log.
That gave me a far more-reasonable ~80,000 records with which I could make Excel cry.2
It looks like my hunch is right. The wordcount of “found” logs on traditional and multi-stage caches has generally decreased over time:
“Did not find” logs, which can be really helpful for cache owners to diagnose problems with their caches, have an even more-pronounced dip:
When I first saw that deep dip on the average length of “did not find” logs, my first thought was to wonder whether the sample might not be representative because the did-not-find rate itself might have fallen over time. But no: the opposite is true:
Strangely, the only place that the trend is reversed is in “found” logs of virtual caches, which have seen a slight increase in verbosity.
Within the limitations of my research (80,000 logs from 500 caches each 10+ years old, near me), there are a handful of clear trends over the last decade:
Are these trends a sign of shortening attention spans? Increased use of mobile phones for logging? Use of emoji and acronyms to pack more detail into shorter messages? I don’t know.
I’d love to see some wider research, perhaps by somebody at Geocaching.com HQ (who has database access and is thus able to easily extract enough data for a wider analysis!). I’m also very interested in whether the identity of the cache finder has an impact on log length: is it impacted by how long ago they started ‘caching? Whether or not they have hidden caches of their own? How many caches they’ve found?
But personally, I’m just pleased to have been able to have a question in the back of my mind and – through a little bit of code and a little bit of data-mashing – have a pretty good go at answering it.
1 I have a dream that someday cache logging could be powered by Webmentions or ActivityPub or some similar decentralised-Web technology, so that cachers can log their finds on any site on which a cache is listed or even on their own site and have all the dots joined-up… but that’s pretty far-fetched I’m afraid. It’s not stopping some of us from experimenting with possible future standards, though…
2 Just for fun, try asking Excel to extrapolate a second-order polynomial trendline across 80,000 pairs of datapoints. Just don’t do it if you’re hoping to use your computer for anything in the next quarter hour.
3 With stricter guidelines on how a “virtual rewards” virtual caches should work than existed for original pre-2005 virtuals, these new virtuals are more-likely than their predecessor to encourage or require longer logs.
This is a repost promoting content originally published elsewhere. See more things Dan's reposted.
…
(Joe reads the text on IE and clicks on “Suggested Sites”)
Me: “Why did you click on that?”
Joe: “I don’t really know what to do, so I thought this would suggest something to me.”
…
Finding adults who’ve got basically no computer experience whatsoever is getting increasingly rare (and already was very uncommon back in 2011 when this was written), and so I can see why Jennifer Morrow, when presented with the serendipitous opportunity to perform some user testing with one, made the very most of the occasion.
As well as being a heart-warming story, this post’s a good reminder that we shouldn’t make assumptions about the level of expertise of our users.
I’m not sure that there’s any age that’s too-young at which to try to cultivate an interest in science. Once a child’s old enough to ask why something is the case, every question poses an opportunity for an experiment! Sometimes a thought experiment is sufficient (“Uncle Dan: why do dogs not wear clothes?”) but other times provide the opportunity for some genuine hands-on experimentation (“Why do we put flowers in water?”). All you have to do is take every question and work out what you’d do if you didn’t know the answer either! A willingness to take any problem with a “let’s find out” mentality teaches children two important things: (a) that while grown-ups will generally know more than them, that nobody has all the answers, and (b) that you can use experiments to help find the answers to questions – even ones that have never been asked before!
Sometimes it takes a little more effort. Kids – like all of us, a lot of the time – can often be quite happy to simply accept the world as-it-is and not ask “why”. But because a fun and educational science activity is a good way to occupy a little one (and remember: all it needs to be science is to ask a question and then try to use evidence to answer it!), I’ve been keeping a list of possible future activities so that we’ve got a nice rainy-day list of things to try. And because we are, these days, in an increasingly-large circle of breeders, I thought I’d share some with you.
Here’s some of the activities we’ve been doing so far (or that I’ve got lined-up for future activities as and when they become appropriate):
So there’s my “now and next” list of science activities that we’ll be playing at over the coming months. I’m always open to more suggestions, though, so if you’re similarly trying to help shape an enquiring and analytical mind, let me know what you’ve been up to!
This is not a blog post about pentesting, or any other kind of software-engineering inspired testing of pens. Nor is it a blog post about the kind of fascination some people have with pens and ink. Instead, this is a blog post about history and psychology.
Recently, JTA asked me what I do when I want to test a pen, and he was surprised with the answer. Before I tell you how I answered, I’ll tell you about what I learned from the conversation. And before that, I’ll tell you about the history of pen testing. And then, finally, I’ll tell you why I think it’s important from a psychological perspective.
Historically, the “breaking in” of a new pen was called a probatio pennae, literally “pen test”, and would typically be a few lines of text or a short proverb: something that demonstrated the pen’s ability to write. For the entire mediaeval period, plus several centuries besides, the principle instrument for writing would be the quill pen: the primary wing feathers of a large bird such as a goose, often hardened in hot ashes, stripped of barbs, and cut down to size with an blade whose purpose lends its name to what we now call a “pen knife”. With such a tool, a scribe would want to be sure that the pen could hold an adequate nibful of ink without splashing or spraying, and – despite the high value of paper – it was clearly essential to write a whole sentence or two to be sure.
A modern ballpoint pen has no such issues, but instead introduces some of its own: a plastic-lined inkwell can be gradually penetrated by the air, causing the ink to dry up; the ball can become stuck and will not turn freely; air bubble can develop within the tube (especially if the pen is stored, or worse-still used, the wrong way up); and, of course, the pen can run out of ink. This typically precipitates its disposal: your biro isn’t built to be re-used for anything except perhaps to perform an emergency tracheotomy, and it’s cheap enough that you don’t want to waste your time repairing it. As a result, our pen tests have become fast, designed to determine within a few seconds whether the pen we’ve got is working or, in the case of a stuck ball, can be made to start working with a sufficiency of scribbling. Our culture of disposal can’t spare the time for any more than a cursory test before we give up and grab the next one.
So what do we write? What is the probatio pennae of our times? It’s been widely-reported (although I can’t find any decent citations) that, upon being offered a new pen to try out, 97% of people will write their own name. Now that statistic smells fishy to me (no good citations anywhere, and 97% of people use 97% as their “virtually all” number, for made-up statistics), but I’ve been testing the hypothesis among friends these last few days, and I’ve gathered enough evidence to convince me that it’s probably the case that many or most people will write their own name to test a pen.
Somebody had presumably asked JTA what he wrote, earlier in the day, because he took the time to tell me that when he tests a new pen, he typically writes the word “hello”.
Now I find that pretty weird. Maybe it’s the software engineer in me, but to me the mark of a good test is that it covers all of the possible cases, in the minimal possible effort. Writing your name is easy because it’s managed by what is popularly-called “muscle memory”: a second-season episode of Castle (correctly) used this as a plot point, when a man suffering from retrograde amnesia was unable to remember his name, but was still able to sign his name because the act of signing it had been rendered, by years of practice, into his procedural memory, which was unaffected by his condition. But writing a word, like “hello”… requires a comprehension of language. Unless he’s tested enough pens to have built a procedural memory of writing “hello” to test pens, JTA’s test has a greater number of neural dependencies, which – with apologies to those of you who aren’t interested in automated software testing – produces what we’d call an unnecessarily “brittle” test.
Me? I just scribble, which my quick survey (and several comparable ones online) show to be probably the second-most popular action to test a pen. Scribbling, to me, simply seems like the minimal test path: the single simplest thing that can be done with a pen that will demonstrate that it’s fit for purpose. I don’t need to test that a new pen can write words, because – to me – writing words in particular is not a function of the pen, but a function of my brain! To me, the pen’s function is simply one of transferring ink to the paper, and any semantic meaning coming from the ink is a product of my intellect, not of the writing implement.
So why is this important? Well: I have a half-baked hypothesis that the choice of what to write with a new pen might be linked to other aspects of our psychology. When I’m developing a new template for a website, for example, I use lorem ipsum text and dummy placeholder images as filler (just occasionally, I’ll use kittens, because kittens are adorable). That’s because the absence of meaning to the words that appear (I don’t read Latin, and even if I did, lorem ipsum is frequently mangled) has no bearing on my comprehension of the design: and, in fact, it can sometimes be a benefit to be deprived of the distraction of legible content.
But I’d hypothesise that people who write words as a probatio pennae would be less-comfortable with illegible placeholder-text in a design than those who drew scribbles or signed their name. I have a notion, from my own experience, that the same parts of the brain that is responsible for judging the quality of a writing implement are used in the judgement of a piece of design work. Hey: maybe if that’s true, graphic designers should have their clients test pens out, in their presence, before they decide whether to use believable filler or lorem ipsum text in the designs they’d like approved.
Or maybe I’m way off base. What do you write when you test a pen?
Some frozen food was delivered to me by courier, packed in a box stuffed with dry ice (frozen carbon dioxide). Not to be deprived of an opportunity, I used the ice to make fog, foggy bubbles, screeching sounds… and to keep my drink cool. Here’s a video of some of the highlights. (I also tried blowing things up, but couldn’t find a plastic bottle with a sufficiently strong outer wall to make the explosion worthwhile)
This little experiment demonstrates that TFT monitors, unlike CRT monitors, seem to output polarised light. But why is this? If you know, leave me a comment. Thanks!