Just wanted to share with you something I found ages ago but only just got around to mentioning – Julia Evans‘ (of Wizard Zines fame) Debugging Mysteries:
Each mystery is a Twine-powered “choose your own adventure” game in which you must diagnose the kind of issue that a software developer might, for
real. I think these are potentially excellent tools for beginner programmers, not just because they provide some information about the topic of each, but because they encourage
cultivating a mindset of the kind of thinking that’s required to get to the bottom of gnarly problems.
This video accompanies a blog post of the same title. The content is basically the same – if you prefer videos, watch this video. If you prefer blog posts, go read
the blog post. If you’re a superfan, try both and spot the differences. You weirdo.
There are a great number of things that I’m bad at. One thing I’m bad at (but that I’m trying to get better at) is being more-accepting of the fact that there are things that I am bad
at.
I’ve also been thinking about how I’m bad at thinking about how I’m bad at thinking about how I’m bad at thinking about…
I’m also particularly bad at choosing suitable stock photos for use in blog posts.
Being Bad
As a young kid, I was a smart cookie. I benefited from being an only child and getting lots of attention from a pair of clever parents, but I was also pretty bright and a quick learner
with an interest in just about anything I tried. This made me appear naturally talented at a great many things, and – pushed-on by the praise of teachers, peers, and others – I
discovered that I could “coast” pretty easily.
But a flair for things will only carry you so far, and a problem with not having to work hard at your education means that you don’t learn how to learn. I got bitten
by this when I was in higher education, when I found that I actually had to work at getting new information to stick in my head (of course, being older makes learning harder
too, as became especially obvious to me during my most-recent qualification)!
Ignore the fact that you’ve now seen me trying to sledge uphill and just accept that I was a clever kid (except at
photography), okay?
A side-effect of these formative experiences is that I grew into an adult who strongly differentiated between two distinct classes of activities:
Things I was good at, either because of talent or because I’d thoroughly studied them already. I experienced people’s admiration and respect when I practised these
things, and it took little effort to stay “on top” of these fields, and
Things I was bad at, because I didn’t have a natural aptitude and hadn’t yet put the time in to learning them. We don’t often give adults external
reinforcement for “trying hard”, and I’d become somewhat addicted to being seen as awesome… so I shied away from things I was “bad at”.
The net result: I missed out on opportunities to learn new things, simply because I didn’t want to be seen as going through the “amateur” phase. In hindsight, that’s
really disappointing! And this “I’m bad at (new) things” attitude definitely fed into the imposter syndrome I felt when I first
started at Automattic.
Being Better
Leaving the Bodleian after 8½ years might have helped stimulate a change in me. I’d carved out a role for myself defined by the fields I knew
best; advancing my career would require that I could learn new things. But beyond that, I benefited from my new employer whose “creed
culture” strongly promotes continuous learning (I’ve vlogged about this before), and from my coach who’s been great at encouraging me towards a growth mindset.
“Good Luck Dan”, my Bodleian buddies said. But perhaps they should’ve said “Keep Learning Dan”.
But perhaps the biggest stimulus to remind me to keep actively learning, even (especially?) when it’s hard, might have been the pandemic. Going slightly crazy with cabin fever during
the second lockdown, I decided to try and teach myself how to play the piano. Turns out I wasn’t alone, as I’ve mentioned before: the pandemic did strange things to us all.
I have no real experience of music; I didn’t even get to play recorder in primary school. And I’ve certainly got no talent for it (I can hear well enough to tell how awful my
singing is, but that’s more a curse than a blessing). Also, every single beginners’ book and video course I looked at starts from the assumption that you’re going to want to “feel” your
way into it, and that just didn’t sit well with the way my brain works.
90% of what I do in front of a piano might be described as “Dan Mucks About (in B Minor)”, but that’s fine by me.
I wanted a theoretical background before I even sat down at a keyboard, so I took a free online course in music theory. Then I started working through a
“beginners’ piano” book we got for the kids. Then I graduated to “first 50 Disney songs”, because I know how virtually all of them sound well enough that I’d be able to hear where I was
going wrong. Since then, I’ve started gradually making my way through a transcription of Einaudi’s Islands. Feeling like I’d got a good handle on what I was supposed to be
doing, I then took inspiration from a book JTA gave me and started trying to improvise.
Most days, I get no more than about 10 minutes on the piano. But little by little, day by day, that’s enough to learn. Nowadays even my inner critic perfectionist can
tolerate hearing myself play. And while I know that I’ll probably never be as good as, say, the average 8-year-old on YouTube, I’m content in my limited capacity.
Let’s start at the very beginning. (A very good place to start.)
If I’m trying to cultivate my wonder syndrome, I need to stay alert for “things I’m bad at” that I could conceivably be better at if
I were just brave enough to try to learn. I’m now proudly an “embarrassingly amateur” pianist, which I’m at-long-last growing to see as better than a being non-pianist.
Off the back of that experience, I’m going to try to spend more time doing things that I’m bad at. And I’d encourage you to do the same.
I last handed in a dissertation almost 16 years ago; that one marked the cumulation of my academic work at Aberystwyth University, then the “University of Wales, Aberystwyth”. Since then I’ve studied programming, pentesting and psychology (the P-subject
Triathalon?)… before returning to university to undertake a masters degree in information security and forensics.
Today, I handed in that dissertation. Thanks to digital hand-ins, I’m able to “hand it in” and then change my mind, make changes, and hand-in a replacement version right up
until the deadline on Wednesday (I’m already on my second version!), so I’ve still got a few evenings left for last-minute proofreads and tweaks. That said, I’m mostly
happy with where it is right now.
I found it motivating to maintain a graph of my dissertation’s “outstanding tasks” where I would see it every day. Also, as it started to get hairy, my word limit.
Writing a dissertation was harder this time around. Things that made it harder included:
Writing a masters-level dissertation rather than a bachelors-level one, naturally.
Opting for a research dissertation rather than an engineering one: I had the choice, and I knew that I’d do better in engineering, but I did research anyway because I
thought that the challenge would be good for me.
Being older! It’s harder to cram information into a late-thirty-something brain than into a young-twenty-something one.
Work: going through the recruitment process for and starting at Automattic ate a lot of my time,
especially as I was used to working part-time at the Bodleian and I’d been turning a little of what would otherwise have been my “freelance work time” into “study time” (last time
around I was working part-time for SmartData, of course).
Life: the kids, our (hopefully) upcoming house move and other commitments are pretty good at getting in the way. Ruth and JTA have been amazing at carving out blocks of time for me to study, especially these last few weekends, which may have made all the
difference.
Despite this thing being big and heavy and dense, it somehow doesn’t seem to fully represent the weight of blood, sweat and tears that went into it.
It feels like less of a bang than last time around, but still sufficient that I’ll breathe a big sigh of relief. I’ve a huge
backlog of things to get on with that I’ve been putting-off until this monster gets finished, but I’m not thinking about them quite yet.
I need a moment to get my bearings again and get used to the fact that once again – and for the first time in several years – I’ll soon be not-a-student. Fun fact, I’ve spent
very-slightly-more than half of my adult life as a registered student: apparently I’m a sucker it, for all that I complain… in fact, I’m already wondering what I can study
next (suggestions welcome!), although I’ve promised myself that I’ll take a couple of years off before I get into anything serious.
(This is, of course, assuming I pass my masters degree, otherwise I might still be a student for a little longer while I “fix” my dissertation!)
A personal highlight was that I got to find a genuine use for Sankey charts and treemaps in my work for perhaps the first time.
If anybody’s curious (and I shan’t blame you if you’re not), here’s my abstract… assuming I don’t go back and change it yet again in the next couple of days (it’s still a little clunky
especially in the final sentence):
Multifactor authentication (MFA), such as the use of a mobile phone in addition to a username and password when logging in to a website, is one of the strongest security enhancements
an individual can add to their online accounts. Compared to alternative enhancements like refraining from the reuse of passwords it’s been shown to be easy and effective. However: MFA
is optional for most consumer-facing Web services supporting MFA, and elective user adoption is well under 10%.
How can user adoption be increased? Delivering security awareness training to users has been shown to help, but the gold standard would be a mechanism to encourage uptake that can be
delivered at the point at which the user first creates an account on a system. This would provide strong protection to an account for its entire life.
Using realistic account signup scenarios delivered to participants’ own computers, an experiment was performed into the use of language surrounding the invitation to adopt MFA. During
the scenarios, participants were exposed to statements designed to either instil fear of hackers or to praise them for setting up an account and considering MFA. The effect on uptake
rates is compared. A follow-up questionnaire asks questions to understand user security behaviours including password and MFA choices and explain their thought processes when
considering each.
No significant difference is found between the use of “fear” and “praise” statements. However, secondary information revealed during the experiment and survey provides recommendations
for service providers to offer MFA after, rather than at, the point of account signup, and for security educators to focus their energies on dispelling user preconceptions about the
convenience, privacy implications, and necessity of MFA.
I keep my life pretty busy and don’t get as much “outside” as I’d like, but when I do I like to get out on an occasional geohashing expedition (like these
ones). I (somewhat badly) explained geohashing in the vlog attached to my expedition 2018-08-07 51 -1, but the short
version is this: an xkcd comic proposed an formula to use a stock market index to generate a pair of random coordinates, impossible to predict in
advance, for each date. Those coordinates are (broadly) repeated for each degree of latitude and longitude throughout the planet, and your challenge is to get to them and discover
what’s there. So it’s like geocaching, except you don’t get to find anything at the end and there’s no guarantee that the destination is even remotely accessible. I love it.
My favourite kind of random pointlessness is summarised by this algorithm.
Most geohashers used to use a MediaWiki-powered website to coordinate their efforts and share their stories, until a different application on the server where it resided got hacked and the wiki got taken down as a precaution.
That was last September, and the community became somewhat “lost” this winter as a result. It didn’t stop us ‘hashing, of course: the algorithm’s open-source and so are many of its
implementations, so I was able to sink into a disgusting hole in November, for example. But we’d lost the digital
“village square” of our community.
My dissertation “burndown” is characterised on my whiteboard by two variables: outstanding issues (blue) and wordcount (red). There are… a few problems.
So I emailed Davean, who does techy things for xkcd, and said that I’d like to take over the Geohashing wiki but that I’d first like (a) his or Randall’s blessing to do so, and ideally
(b) a backup of the pages of the site as it last-stood. Apparently I thought that my new job plus finishing my dissertation plus trying to move house plus all of the usual
things I fill my time with wasn’t enough and I needed a mini side-project, because when I finally got the go-ahead at the end of last month I (re)launched geohashing.site. Take a look, if you like. If you’ve never been Geohashing before, there’s never been a more-obscure time to start!
My implementation of the site is mobile-friendly for the benefit of people who might want to use it while out in a muddy ditch. For example. Just hypothetically.
Luckily, it’s not been a significant time-sink for me: members of the geohashing community quickly stepped up to help me modernise content, fix bots, update hyperlinks and the like. I
took the opportunity to fix a few things that had always bugged me about the old site, like the mobile-unfriendly interface and the inability to upload GPX files, and laid the groundwork to make bigger changes down the road (like changing the way that inline maps are displayed, a popular community request).
So yeah: Geohashing’s back, not that it ever went away, and I got to be part of the mission to make it so. I feel like I am, as geohashers say… out standing in my field.
Last week I tweeted a cow-based academic publishing analogy in response to the prompt in the title, and the replies and quote-tweets extended the metaphor so gloriously, so
creatively, so bleakly and hilariously at the same time, that I’ve pulled my favourites together below.
Here’s the original tweet:
Cows make milk. They milk themselves.
Other cows check the milk (for free).
Cows – get this – PAY THE FARMER to take the milk away.
When I took a diversion from my various computer science related qualifications to study psychotherapy for a while, I was amazed to discover how fortunate we computer
scientists are that so much of our literature is published open access. It probably comes from the culture of the discipline, whose forefathers were publishing their work as
open-source software or on the Internet long before academic journals reached the online space. But even here, there’s journal drama and all the kinds of problems that Ned (and the
people who replied to his tweet) joke about.
That moment when you realise, to your immense surprise, that the research you’ve spent most of the year on might actually demonstrate the thing you set out to test after all. 😲
Screw you, null hypothesis.
One of the best things about working atThe Bodleian Libraries, University of Oxford? Pretending to be a PhD student for a photo shoot! Watch out for me
appearing in a website near you…
My team and I do get up to some unusual stuff, it’s true. I took part in this photoshoot, too:
I’m absolutely not above selling out myself and my family for the benefit of some stock photos for the University, it seems. The sharp-eyed might even have spotted the kids in this video promoting the Ashmolean or a recent tweet by the Bodleian…
Results day today, and so I finally get to find out whether or not I get a degree in exchange for my last five years at University. And I do. I’m now entitled to put letters after my
name, which is nice.
I’ve got a lower second, which is (I know) less than I’m capable of, but considering my resits and other lark last year, it’s exactly what I expected, so that’s great. Was damn pleased
to see that my dissertation got a first.
Now I suppose I’d better get on with the rest of my life.
I’ve solved the former: Claire needs to move her car (which is parked on double-yellows outside) or she’ll get ticketed when the morning wardens come by (morning wardens? they’re like
traffic wardens, but they put tickets on people who still look half-asleep). The latter? No idea.
Yay; we’re off to the Borth Animalarium today, to look at meerkats! Followed by Troma Night!
My ‘Online Bank’ project isn’t going very well. So far it allows you to add Books to a Cart and get the total cost of them all. Which isn’t terribly useful, because that sounds more
like a bookstore to me than an online bank… but I couldn’t find an example online about how to use EJBs to make an online bank, just a bookstore. D’oh.
[this post has been partially damaged during a server failure on Sunday 11th July 2004, and it has been possible to recover only a part of it]
I handed in my dissertation yesterday. What a farce. Here’s the approximate order of things.
08:30 – Get up. Compile a postscript (.ps) copy of my dissertation, and upload both this and the .tex source files to central.aber.ac.uk. Start walking up to campus (Bryn offers to give
me a lift, but I feel energetic, so I bound on up the hill).
09:00 – Reach campus and pay for £5 of printer credit (100 pages). Find a workstation room, log into central, and lpr -Puserarea diss-final.ps (print) it. Marvellous. Pick
up the printout.
09:15 – Drop my (printed) dissertation off at the Library to be hardback bound. Everything’s going splendidly. Trek back down town. The hand-in window is 14:00-16:00, so I’ve got loads
of time.
13:30 – Arrive back on campus, this time with two CDs (containing the source code and sample data for the project). I buy sticky things
from the Union with which to attach them to the inside cover of my dissertation, and then trek to the Library to pick up the masterpiece.
13:45 – Hmm. The binding office seems to be closed. Guess they’re on lunch. I go to return a library book from the Physical Sciences Library, …
Update, 11 January 2020: As the tail-end of this post appears to be lost forever, I’ll fill in the essence of it from memory:
after a leisurely morning/early afternoon of getting my dissertation printed and bound for delivery, well-ahead of the deadline later in the day and thus avoiding the mad rush for the
printers and binders later in the day, I arrived at the hand-in point only to be told I was supposed to be handing over two copies, not one, and so I ended up caught up in the
mad rush I’d been smugly avoiding after all.
[this post has been partially damaged during a server failure on Sunday 11th July 2004, and it has been possible to recover only a part of it]
I’m looking for help proofreading my dissertation. If you’ve been invited to, or you’d like to help, please go to https://danq.me/diss/, download the latest version, and post any
comments here.
You will need a password. To ensure that only invited parties can get hold of the password, you’ll need to prove your identity. The following groups are permitted to log in:
Members of Troma Night: go to the Troma Night web site and log in: the password will appear on
the front page, underneath the words ‘Upcoming Events’.
People listed as LiveJournal friends of Fiona: go to this LiveJournal post by Fiona (you’ll need
to be logged in and on her Friends list).
People who can guess the password – it’s the second half of the name of the project of my dissertation, in lower case, with the final letter replaced with the first vowel in the
word that is the name of the logo of the organisation that benfits from my project.
[this post has been partially damaged during a server failure on Sunday 11th July 2004, and it has been possible to recover only a part of it]
[chez geek card]
Yay. Now I’m in a fab bouncey mood and ready to crack on with the next 10,000 words of my dissertation.
People have kindly been offering to proof-read it for me on Sunday night – this is most welcome: if anybody else wants to, you can too: just drop me a comment or a message or something,
and I’ll e-mail you it. I presume you’ll all prefer Acrobat .PDFs than PostScript .PS files, yeh?
On which note; everybody’s being really considerate of my need to get this thing done – leaving me to do it where they’re likely to be a distraction; not suggesting really cool things
we could be doing right now (except for the above card, ahem), etc. Thank you all, guys!
Yes! Yes! Yes! I’m about two-thirds of the way through the development of the new Troma Night
website (between bouts of revision). Should be ready within the next 12 hours. Fab.
If you’re a Troma Night person, go visit www.tromanight.co.uk tonight (Wednesday night).
